Hi read the following URL, it will answer your question.
Kind regards
Thanks for the quick response, and sorry, this didn’t answer my question. I don’t think I explained correctly. What I am trying to achieve is the following…
On a domain-based Multisite install where each sub site is mapped to the client’s own domain like this, subsite-one = client-one.com, subsite-two = client-two.com, etc. I am trying to achieve client-one.com/new-login, client-two.com/new-login, etc.
When I enable the “Rename login page” feature for client-one.com it gives me client-one.com/new-login, just as I want, but it doesn’t do this for client-two.com, client-three.com, nor is the “Rename login page” feature available in client-two.com or client-three.com’s dashboards.
That’s why I asked about installing the plugin on each subsite as opposed to the Network activation option, to achieve client-one.com/new-login, client-two.com/new-login, etc.
I hope that made sense.
Thanks,
Dana
Hi Dana,
Currently some of the features such as the whole of the “Brute Force” menu are not available at the subsite level for multi-site installations.
We will look at making some of these (such as the rename login page feature) available for subsites in a future release.
The reason for the current behaviour is historical – previously we only really had the cookie based brute force feature in the “Brute Force” menu and this was going to be very tricky to implement for subsites so we left it out.
The rename login feature might be easier to include for subsite functionality so we will look at doing that.
Thanks for the info and thank you for this plugin! I look forward to the “rename login feature” making it into multisite in future releases. I would recommend this plugin to anyone who asked about security.
Thanks again,
Dana