Login leads to critical error or 500 error after upgrade to 1.3.22

  • Resolved larssg

    (@larssg)


    3 years, 6 months ago

    After upgrading to 1.3.22, users are no longer able to log in successfully. Logging in leads to either a critical error page or a 500 error. Once this happens, the user won’t be able to access to the site at all.

    I’m seeing a bunch of errors about memory in the Apache logs, like so:
    PHP Fatal Error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /opt/bitnami/apps/wordpress/htdocs/wp-includes/class-wp-user.php (in various different files).

    Disabling plugin fixes the issue. The issue with the previous version causing a critical error also affected our site.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author lukeseager

    (@lukeseager)

    Thanks for the information, apologies for the issue. 1.3.22 was an attempt to re-introduce some code from the previous version which broke (the code had been updated). It’s unclear exactly what the issue is, as I can’t replicate a 500 error on any of my servers.

    I’ll roll back the offending code and push a new version out.

    Plugin Author lukeseager

    (@lukeseager)

    An update has now been pushed. Please take a look and let me know if there are still issues with your website, thanks.

    Thread Starter larssg

    (@larssg)

    Yes, that fixes it, thanks. If you ever want me to test a release along these lines before you push it out, happy to do that, just ping me here.

    Plugin Author lukeseager

    (@lukeseager)

    Great news. If you’d like to join the beta programme, please visit the Account page of Persistent Login and tick the ‘join the beta program’ box.

    Ideally, this should be done on a testing/local server to avoid potential issues with a live website.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Login leads to critical error or 500 error after upgrade to 1.3.22’ is closed to new replies.