Suppose it works like you want.
site.com/newregister –> site.com/newregister?action=register
or
site.com/newregister –> site.com/newregister
At the bottom of the register screen there will be 2 links named “Log in” and “Lost your password?”. Hovering over these links with the mouse pointer will still show:
site.com/mynewlogin
(site.com/mynewlogin?action=lostpassword)
Don’t get me wrong, I agree with you. But it looks like there are other places where the secret WP Dashboard slug is revealed.
It is most visible in the address bar of the browser but a smart user can hover with the mouse pointer over the “Log in” and “Lost your password?” links and still find out …
Anyway this feature does turn out to have a bug in the code as the iTSec plugin adds an invalid Apache RewriteRule line to the .htaccess file for the new register slug (the code for nginx is correct):
RewriteRule ^(/)?newregister/?$ /wplogin?action=register [QSA,L]
“wplogin” is the default slug when you enable the “Hide Backend” feature for the first time.
But when you specify your own slug, “wplogin” should be replaced with with your slug …(mynewlogin):
RewriteRule ^(/)?newregister/?$ /mynewlogin?action=register [QSA,L]
site.com/newregister/ url will now function as you wish …
however site.com/newregister still not …
I think the register slug feature needs some serious code rewriting …
dwinden
