Different Fatal Error after upgrading to Version 2.11

  • Resolved solcryss

    (@solcryss)


    2 years, 5 months ago

    Hello!

    I’ve encountered a different Fatal Error to the other people for this latest plugin update.

    Information:
    PHP 7.4
    WordPress 5.9.3
    Previous Post SMTP version 2.0.27

    Error:
    PHP Fatal error: Class Office365PostSMTP\Transport contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (PostmanTransport::getLogoURL) in /home/public_html/wp-content/plugins/post-smtp-extension-office365/inc/Transport.php on line 9

    I had to update, as I was getting some odd errors about an invalid state and invalid auth tokens.

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

  • Same here. Cannot activate due to above error.
    PHP 8.1
    WP 6.0

    Thanks

    Plugin Support M Haseeb

    (@haseeb0001)

    are you using Office 365 extension?

    you can manually downgrade the plugin from here, (Scroll down and select a specific version to download, 2.0.27)

    In meantime, we are looking into this issue and will try to release an updated version asap.

    Thanks

    @matc @solcryss

    Hello

    Yes, using Office 365 extension.
    Rolling back to 2.0.27 has resolved this for now. Thanks.

    Plugin Support M Haseeb

    (@haseeb0001)

    @matc Great thanks for the update, we are working on it and will release the new version of Office 365 Extension soon.

    Thanks

    Thread Starter solcryss

    (@solcryss)

    Yes, I was also using Office 365 extension.

    I know it was “taken down” from the website while you were upgrading it.

    I had already downgraded to an older version.

    I’ll wait until the new version of the O365 extension is released.

    Thank you.

    Plugin Support M Haseeb

    (@haseeb0001)

    @solcryss

    In the next few days we will launch this extension, please visit our website after a few days to get this Extension updates.

    Thanks

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Different Fatal Error after upgrading to Version 2.11’ is closed to new replies.