v2.0.2 Causes Error 500

  • Resolved harpo1984

    (@harpo1984)


    4 years, 9 months ago

    Hi there,

    The plugin worked correctly up to v2.0.1 but updating to v2.0.2 broke one of my sites causing a site-wide error 500 on the frontend. The wp-admin areas were still accessible but I didn’t receive an email letting me know there was a fatal error and the cause.

    I checked server logs and also enabled debugging for the specific website and no errors are produced which is not helpful. Disabling the plugin brings the site back online.

    I assume it’s an edge case as my other sites are fine. Perhaps something to do with your change:

    Adds in an “if exists” check before checking the settings values

    Kind regards,

    Simon

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

    (@jaysupport)

    Hi Simon,

    It sounds like this might be a coincidence. The change you referenced was the only change in 2.0.2. It just checks to see if the object that points to the settings panel exists before running. It doesn’t add or change anything in the way the plugin works. It just makes sure that, if, for some reason, your site tries to load objects and functions before the plugin finishes its setup, like was the case for one user running the command line interface, the plugin doesn’t try and load anything that doesn’t exist.

    Perhaps the update didn’t fully install, or install correctly, on your site. You could try deleting the plugin and re-installing version 2.0.2.

    Also, if you wanted to roll back to a previous version, they’re available here: https://www.ads-software.com/plugins/business-profile/advanced/

    Thread Starter harpo1984

    (@harpo1984)

    Hi @jaysupport

    I rolled the plugin back to 2.0.1 and got the sitewide Error 500 on the frontend again. Nothing in the WP Debug file or server logs…really strange.

    I rolled back to 2.0.0 and everything worked again…but without error information, I suppose that isn’t much help.

    The site is Bangor Cabs.

    Kind regards,

    Simon

    Plugin Support jaysupport

    (@jaysupport)

    Hi Simon,

    Have you since tried re-updating to 2.0.2, to see if it was just a coincidence with the initial update?

    Like you referenced, an internal server error could be anything and, without some more precise information about the error, it would be difficult to troubleshoot. Did you recently update or install any other plugins or your theme? A lot of times a conflict causes an error like this. You could always test by deactivating other plugins.

    Checking the php error logs on your server might also provide more info on an exact error, if you aren’t seeing anything from the wp debug.

    Thread Starter harpo1984

    (@harpo1984)

    Hi @jaysupport

    I did try re-updating (the same issue occurred ) I’ve not tried a fresh install yet of the plugin, that might help.

    There is nothing showing in the server logs, I checked those…it’s really strange. I’ve not had time to roll up a staging site yet and deactivate plugins one by one to see if there is a conflict.

    A fresh install will be the next thing I try.

    Kind regards,

    Simon

    Thread Starter harpo1984

    (@harpo1984)

    @jaysupport

    The issue is now resolved.

    Steps to resolve as you suggested:

    1. Deactivate the plugin
    2. Delete the plugin
    3. Install the plugin again from the repository

    Kind regards,

    Simon

    • This reply was modified 4 years, 9 months ago by harpo1984. Reason: List Formatting
    • This reply was modified 4 years, 9 months ago by harpo1984. Reason: List Formatting
Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘v2.0.2 Causes Error 500’ is closed to new replies.