-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vor dem Redirect Prüfen, auf aktuelle URL prüfen #13
Comments
@dnaber-de Welche Prüfung meinst du, direkt in der Methode 'redirect()`? |
Es gab in Zusammenspiel mit gehookten Login-Pages (nicht wp-login.php) Probleme. Es kam zu einer Schleife. Das wurde aber schon behoben, ob seitens Authenticator oder projektbezogen weiß ich gerade nicht. Ich schau mir das noch mal an. |
Danke dir! Ansonsten schließen wir den Issue und können ggf. wp.org updaten, was notwendig wäre, wegen eines Bugs. |
@dnaber-de Kannst du das bei Gelegenheit prüfen, dann wäre 1.2 fertig. |
I suggest to use English as language for issues. I think the problem still persists, theoretically. We check for |
Thanks for your time and effort. The language for issues is all the same for me, but if we discus without other guys and dolls, then is German much easier for me. |
I have updated the prev. fix for this issue (17acc20). In my case the prev. fix doesnt work if i had a custom login page and add a filter for my login_url. Example: page-login.php - Added a blank page with url /login/
functions.php
Testcases:
|
About 17acc20: What happens if you request a sub-page with the permalink Furthermore I think we should compare the complete login URL (including the host) to respect setups where logins might be combined on one site in a multisite. |
Prüfen, ob die aktuelle Seite nicht schon die Login-Page ist, um Loops zu vermeiden. Der check auf
$pagenow
läuft bei Custom Login-Pages ins leere.The text was updated successfully, but these errors were encountered: