3.3 Fatal Error with Login Lock

@mark … and I would like to venture that many plugin developers request that problems with their plugins be reported here at www.ads-software.com. That is where the “what others are saying” leads to …

But, what I’m here to report is that v2.2.6 is working at my site. Thanks for getting a fix out there. ??

For the record of those following this thread, the is_rtl() fatal error still exists in 2.2.6.

Here is how the upgrade to v2.2.6 went for me…

After deleting the old version of the plugin from my site, I installed it again through wp-admin. When activated, the plugin reported a header error but not the is_rtl() error. I changed the URL in the address bar to be my domain’s wp-admin address and the dashboard came up.

When I navigated to the plugins tab, Login Lock was not activated. I manually activated it and there were no errors reported.

This morning, I upgraded the plugin at a client site and it slipped right into place, as it should do.

Just telling my story. ??

Just to add to the mix of people offended by Mark (above)-its pretty useless to just pop into a thread and chastise people who are having problems. Wouldn’t your time be better spent elsewhere?

To other users I have had all the problems set forth above, and tried all the above-offered solutions, to no avail. Even version 2.2.7 of this plugin does not work, and the creator dire ct you to go to its wordpress security page, which gives you a 404 error. At the creators website, you are directed to contact them: https://wpsecurity.net/contact-us/

have no idea if they can help, stay tuned.