I’m pinging my network of devs to see if there is a conditional for those pages. So far, I haven’t found anything other than CSS classes, which won’t stop the plugin.
Yes, this is one of the only real failings I’ve seen with this plugin.
I know not many people use password protected pages, so I imagine mine is not an urgent issue.
Just thinking outside the box here, but even a timer option which disables the stealth plugin between x and y hour would at least allow me to send a note to client stating, “you may access page X between 4 to 6pm today, yada yada.”
As it is now, if I wish for client to view my password protected page I have to manually deactivate plugin then remember to reactivate it later. Sort of annoying.
I’m taking these things into consideration for the next version after this WP 3.6 update. The best plugins are simple, but I see this spiraling out of scope with too much effort. I didn’t mean for it to be an all-in-one solution – just to block the brute force attempts.
v4.0 will add add-on ability for such features while leaving core alone, how it is now, only even more streamlined.
This has been resolved if you update to v4.0.0 now. There is no longer a redirect at the login page itself.
Please follow-up via e-mail if I need to re-visit this after you enter the auth code.
