Critical error + server error 500 since updating to 1.8.5

  • Resolved jfleduc

    (@jfleduc)


    2 years, 9 months ago

    Hello,

    I successfully set-up this plugin in early September. We have been using it ever since with great ease.

    Since updating to 1.8.5, my website was unable to be updated at all. If I tried to add a new page or post in the WordPress backend, I would get a “Critical error.” message. If I tried to update the content of a page via Elementor, I would get Server error 500.

    Took a while to figure out your plugin was causing this issue. It’s in fact Cpanel’s support staff that told us to turn off the plugin and indeed that immediately fixed the issue.

    1- Is there any way to gain access to version 1.8.4 from you again?
    2- How can I help you troubleshoot this further?

    We are using WordPress with Hello theme and Elementor pro, everything latest versions. We are self hosting on a company Linux server with Cpanel.

    Thank you!

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

  • @jfleduc I’d need the PHP error log from your server. It may be your version of PHP doesn’t support the Scoper library I’m using to namespace the classes.

    As well as the log, can you let me know your php version, and the version of WordPress you’re using?

    Thread Starter jfleduc

    (@jfleduc)

    PHP Error log :

    [06-Jan-2022 16:28:49 UTC] PHP Fatal error: Classes\Mail_Integration_365\Mail::send(): The script tried to execute a method or access a property of an incomplete object. Please ensure that the class definition "TheNetworg\OAuth2\Client\Token\AccessToken" of the object you are trying to operate on was loaded _before_ unserialize() gets called or provide an autoloader to load the class definition in /home/jfleduc/public_html/wp-content/plugins/mail-integration-365/classes/mail_integration_365/mail.php on line 151

    PHP v.: 7.4.27-1.1.3.cpanel.x86_64
    Wordpress v.: 5.8.2

    @jfleduc so the issue is your old access token object is still stored in the database, and that is referencing methods within class libraries that are now namespaced to avoid conflicts with other plugins utilising the same libraries. As such, PHP doesn’t recognise the object in the database.

    The way round this is to reauthorize the plugin with office 365 which will overwrite the existing access token object in the database with the new namespaced object.

    Thread Starter jfleduc

    (@jfleduc)

    Hi,

    Yes, it worked! I also just saw in the settings tab that you added the info to re-authorise since 1.8.3. I’ll know for next time, thanks for your help!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Critical error + server error 500 since updating to 1.8.5’ is closed to new replies.