WordPress.org

Ready to get started?Download WordPress

Forums

Login Lock
3.3 Fatal Error with Login Lock (20 posts)

  1. cforant
    Member
    Posted 3 years ago #

    is_rtl function fatal error with 3.3 and Login Lock. Disabling plugin averts error.

    http://wordpress.org/extend/plugins/login-lock/

  2. Marj Wyatt
    Member
    Posted 3 years ago #

    Apparently the developer needs to look into it because I am having that same issue today. Because I had logged into my site in the morning and didn't notice until I went back to the dashboard to ocheck something at mid-day, it appears to be spontaneous.

    The Login Lock plugin version is 2.2.3

  3. Marj Wyatt
    Member
    Posted 3 years ago #

    I'm very surprised that the developer has not responded to this critical error. After upgrading my site to WP 3.3, everything worked fine for a couple of days and then this error kept me from accessing the wp-admin area:

    Fatal error: Call to undefined function is_rtl() in /home/creat361/public_html/mydomainname.com/wp-includes/general-template.php on line 2102

    This does not affect the operation of the site for visitors, only for admins.

  4. rodwreck
    Member
    Posted 3 years ago #

  5. Daniel Convissor
    Member
    Posted 3 years ago #

    This seems like a bug in the order that files are being included by WordPress' core. I've opened a ticket about it:
    http://core.trac.wordpress.org/ticket/19913

  6. Daniel Convissor
    Member
    Posted 3 years ago #

    I committed several fixes for the login-lock plugin and put them up at https://github.com/convissor/login-lock

  7. Marj Wyatt
    Member
    Posted 3 years ago #

    @Daniel ... I went to your link and downloaded loginlock.php. I renamed the existing script on my server and uploaded the newest one from github.com.

    Whatever changes were made to that script did not help me at all.

    Yes, I am aware that I could go through and troubleshoot plugin incompatibility but I can't imagine which of my installed and activated plugins that I'm willing to live without ... even if one does present as being in conflict.

    My thinking is pretty simple on this. Login Lock was playing nice with all my other plugins prior to the last WP update. None of what I consider to be my other essential plugins are reporting an error after the WP upgrade. It seems "logical" to assume that the problem is not with my previously installed and working plugins but rather with the Login Lock plugin itself.

    I do hope this problem gets fixed soon...

  8. Daniel Convissor
    Member
    Posted 3 years ago #

    @MarjWyatt Things are out of sync on your system. Deactivate the plugin. Delete the old file (or move it to somewhere outside of your WP install). Put in my loginlock.php file. Then activate the plugin.

  9. Marj Wyatt
    Member
    Posted 3 years ago #

    @Daniel ...

    I did exactly as you described here:

    Deactivate the plugin. Delete the old file (or move it to somewhere outside of your WP install). Put in my loginlock.php file. Then activate the plugin.

    Error ... can't remember what

    I deleted the files from my server and uploaded this zip file (convissor-login-lock-2d95779.zip) from GitHub, and activated it as if it was the plugin.

    Error ... bad header

    Fatal error: Call to undefined function login_header() in /home/myaccount/public_html/getincomeblog.com/wp-content/plugins/convissor-login-lock-2d95779/loginlock.php on line 614

    I downloaded plugin from extends.wordpress.org, uploaded file through add new plugin dashboard. I did not activate it until I downloaded the latest loginlock.php from GetHub and replaced that file, using your earlier instructions.

    The result was then that the only access which I had to my wp-admin dashboard was to view your plugin script through GitHub.

    I'm about to give up but will try something else, if you have a suggestion.

  10. Mark
    Member
    Plugin Author

    Posted 3 years ago #

    I just pushed v2.2.4 into the plugins repository. Hopefully I got the fix for the " is_rtl() is not a function " problem resolved. I'm not sure though since I don't have such a system to test with.

  11. Mark
    Member
    Plugin Author

    Posted 3 years ago #

    @MarjWyatt : You shouldn't be surprise. The readme file clearly tells people how to report bugs and get support - which incidentally doesn't include posting to this forum.

  12. Marj Wyatt
    Member
    Posted 3 years ago #

    @Mike ... I didn't realize the WordPress forum was an inappropriate place to converse about plugin problems. Most people install plugins directly through wp-admin and few would think to open the plugin folder and read a readme.txt file. I'm sort of a "grizzled veteran" and it didn't occur to me to do that...

    But, more importantly, does your update regarding 2.2.4 mean that an update notification will soon appear in the WordPress Updates area?

  13. Mark
    Member
    Plugin Author

    Posted 3 years ago #

    Prolly should get in the habit of inspecting the readme for plugins since invariably that's the ONLY way we devs have of communicating info to users of our plugins...

    At the same time - only few plugin devs have time to cruise the forums here. We're usually busy writing code and paying bills - since these plugins are free we gotta make some money elsewhere.

    Your dashboard should eventually update to indicate a new version is available.

  14. Daniel Convissor
    Member
    Posted 3 years ago #

    Alas, the 2.2.4 release does not fix the is_rtl() for people trying to log in after the administrator has locked everyone out. A _workaround_ for it is on GitHub (commit 127ff125f2).

  15. cforant
    Member
    Posted 3 years ago #

    As the original poster, I take offense to the comment from Mark...This is absolutely the appropriate place to write this type of post. When an upgrade causes issues, whether from WP or a plugin, people need to know before they get into a mess that they are not expecting.

    I reported this to the community in a nice way...because bugs happen...its the nature of the beast. This community needs to look out for each other.

    Just a side note...I DID report the bug properly at the same time of the post.

  16. Mark
    Member
    Plugin Author

    Posted 3 years ago #

    It's appropriate to post here in terms of WP, but if you're expecting support and a bug fix to the plugin you need to follow the instructions in the readme ( you said you did ). Many, many, devs have their own support forums and other support methods and do not have time to check this forum, particularly when a plugin is given away freely and generates no revenue to cover the time involved with cruising the forum...

  17. Marj Wyatt
    Member
    Posted 3 years ago #

    @Mark ... and I would like to venture that many plugin developers request that problems with their plugins be reported here at WordPress.org. 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. :)

  18. Daniel Convissor
    Member
    Posted 3 years ago #

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

  19. Marj Wyatt
    Member
    Posted 3 years ago #

    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. :)

  20. lajuice
    Member
    Posted 2 years ago #

    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.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic