Problem with “Change Login URL” and “Redirect After Logout”

>> When I activate the “Change Login URL” option, when the user or the administrator logs out, it sends me to “/wp-login.php?admin-md&redirect=false“, which is wrong, by default it should reload the login page of the user, or administrator.

Not sure I understand “reload the login page of the user / admin”… did you mean back to /admin-md/?

>> In addition, even if I have changed the wp-admin slug to another, when I follow the link mentioned above, I can easily log in to the system, either as an administrator or as a user. That is wrong.

It should redirect to a /not_found/ URL if you’ve changed the login slug. Not sure why you were able to login with the old slug.

>> the “Redirect After Logout” option doesn’t work well (it doesn’t take the root directory as home and it doesn’t take some pages, at least in my case)

You’ll have to be more detailed. What do you mean by “root directory as home”? What did you enter in the logout redirect settings? What pages were some examples where the redirect did not work?

>> it has problems when working in several languages with plugins like WPML (it doesn’t allows you to select different slugs for each language)

That functionality has not been built… so, it’s not “a problem”… it’s just simply is not there yet.

Hey Qirouslad, I acknowlodge when using the “change login url” the /wp-admin slug still redirects to wp-login.php. When you go to wp-login.php it correctly shows a blank page. Needs a little tweak. Keep up the good work!

@qriouslad

Sorry, it is difficult for me to explain the problems correctly, since I use Google translation (my English is a programmer’s, not a translator’s). This weekend, I’ll try to do it with images.

Regards.

It’s happening to me too: even if I have changed the Login URL to something else, the /wp-admin url is still working, therefore creating a different login url turns out to be useless…

Is there a way to fix this?

@boomerangz @studio84digital I think I understand your confusion. When you set a custom login URL, e.g. https://www.example.com/backend/, that custom login URL will redirect to https://www.example.com/wp-login.php?backend&redirect=false. This is by design. Logging out will also show that redirected URL/page, which makes sense since the user already knows the custom login URL/slug, why hide it after logout?

Hackers will still need to guess the ‘backend’ portion of the URL eitherway, which is the point of using the custom slug in the first place…. so that no one can easily guess it.

WIth the custom login slug enabled, the other default behaviour is as follows: anyone trying to visit https://www.example.com/wp-admin/ or https://www.example.com/wp-login.php will be redirected to https://www.example.com/not_found/ whichi is 404 error page.

This is a test site I created with a ‘backend’ custom slug (will be live for 7 days). Try clicking on any of the links below to see the above behaviours:

• https://amused-ape-gipo.instawp.xyz/backend/ – redirect to login URL
• https://amused-ape-gipo.instawp.xyz/wp-admin/ – redirect to 404 page
• https://amused-ape-gipo.instawp.xyz/wp-login.php – redirect to 404 page

I hope that clarifies things. Marking this resolved for now.

Hello @qriouslad,

Will this feature be compatible with multi-language slugs with WPML in the Pro version?

Greetings.

@boomerangz I haven’t tested the current functionality in WPML site. Have you tested it and found it’s not compatible? If so, can you provide some details on how it’s incompatible?