• Hi, I’m not sure if this is a bug but after the plugin is deactivated and then activated again, the hide login name that you set no longer works (nor does wp-admin) and shows a 404. On one site I’ve had to completely remove the plugin in order to get wp-admin to work at all.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Jelena

    (@jmisic)

    Hi,

    Do you use any type of page cache? Caching plugin maybe? If yes, please clear and then completely disable it and test.

    As for locking out of the site, whenever this happens, best is to use a forceoff method outlined here. This will keep plugin active allowing you to log into that site and change settings.

    We also have this guide you may find helpful:
    https://help.getshieldsecurity.com/article/119-im-blocked-blacklisted-by-the-shield-how-to-unblock-and-prevent-this

    Hope this helps…

    Regards,

    Jelena

    Plugin Author Paul

    (@paultgoodchild)

    This almost certainly a problem relating to page caching, or some sort of page optimisation.

    ANY time you see anything strange or unexpected in the content you see, you should always disable any caching or optimisation plugins: https://getshieldsecurity.com/blog/5-golden-rules-wordpress-site-optimisation/

    Thread Starter dianemk

    (@dianemk)

    Two of the sites were still being built so no caching plugins were installed yet, nor any server side caching. I had the same thing in incognito.
    Anyway just thought I’d let you know.

    Plugin Author Paul

    (@paultgoodchild)

    Was your IP address whitelisted?

    Thread Starter dianemk

    (@dianemk)

    I think so – it detects the IP as part of the set up process doesn’t it? It’s always correct. If it’s not part of the set up process then no. I do sometimes leave the full Shield set up until the end of the build, so on the sites I’m still building then there’s a chance I’d not gone through the full set up yet, so possibly no in those cases.

    I use Shield on 60+ sites and I’m very happy with it. I was just letting you know in case it was a bug as it was the same problem on a few sites after deactivating/activating.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Log in Bug after deactivate/activate’ is closed to new replies.