Fatal 500 error when upgrading plugin to v1.17.6

  • Resolved Dave McHale

    (@dmchale)


    2 years, 1 month ago

    I tried to upgrade the plugin this evening and my whole site crashed. I was able to go back to my backup, but I’m attaching the relevant line from my debug.log

    Thanks in advance if you have any advice, or can address the issue in a new patch!

    [08-Mar-2022 01:53:18 UTC] PHP Fatal error: Uncaught Error: Interface ‘Psr\Container\ContainerInterface’ not found in /home/customer/www/CLIENT_FOLDER/public_html/wp-content/plugins/flexible-shipping-ups/vendor_prefixed/wpdesk/wp-persistence/src/PersistentContainer.php:13
    Stack trace:
    #0 /home/customer/www/CLIENT_FOLDER/public_html/wp-content/plugins/flexible-shipping-ups/vendor/composer/ClassLoader.php(444): include()
    #1 /home/customer/www/CLIENT_FOLDER/public_html/wp-content/plugins/flexible-shipping-ups/vendor/composer/ClassLoader.php(322): Composer\Autoload\includeFile(‘/home/customer/…’)
    #2 [internal function]: Composer\Autoload\ClassLoader->loadClass(‘UpsFreeVendor\\W…’)
    #3 /home/customer/www/CLIENT_FOLDER/public_html/wp-content/plugins/flexible-shipping-ups/vendor_prefixed/wpdesk/wp-persistence/src/Adapter/WooCommerce/WooCommerceSessionContainer.php(11): spl_autoload_call(‘UpsFreeVendor\\W…’)
    #4 /home/customer/www/CLIENT_FOLDER/public_html/wp-content/plugins/flexible-shipping-ups/vendor/composer/ClassLoader.php(444): include(‘/home/customer/… in /home/customer/www/CLIENT_FOLDER/public_html/wp-content/plugins/flexible-shipping-ups/vendor_prefixed/wpdesk/wp-persistence/src/PersistentContainer.php on line 13

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

    (@burnagielk)

    2 years, 1 month ago

    Hi @dmchale thanks for contacting us.

    I would kindly ask you to try to update the plugin one more time. If this error occurs again then please try to upload the plugin via FTP. If this doesn’t work then I recommend you contact your server admin with a request to check opcache settings.

    Let us know if my proposition won’t help. We will try to find another solution.

    Best regards,
    Karolina

    Thread Starter Dave McHale

    (@dmchale)

    2 years, 1 month ago

    Appreciate the quick response @burnagielk

    Unfortunately I did try to reinstall from the repository as well as FTP to the server before I made this thread; neither method worked on my server.

    Can you provide any additional information on what our host should be looking for re: the opcache settings? If I simply ask them to “check the settings”, I’m afraid their support reps may not know what to do with that information.

    Cheers!

    burnagielk

    (@burnagielk)

    2 years, 1 month ago

    Dear @dmchale thanks for the update.
    Our developer’s team is looking into this issue. I will let you know asap what to do next.

    Best regards,
    Karolina

    Thread Starter Dave McHale

    (@dmchale)

    2 years, 1 month ago

    hello @burnagielk

    Don’t want to be a nag, but any updates on this? Right now this pending plugin update is a ticking bomb ready to go off if my client were to try and upgrade plugins on their own (which they are known to do), so I’m hopeful for a resolution soon. Thanks!

    burnagielk

    (@burnagielk)

    2 years, 1 month ago

    Hi @dmchale, thanks for reaching us. I am glad to inform you that we issued a new version of the update. Now, update should be available without any problems. Please verify if you can download the new version 1.17.7. Also, I would be thankful if you let me know if everything works.

    Best regards,
    Karolina

    Thread Starter Dave McHale

    (@dmchale)

    2 years, 1 month ago

    Hi @burnagielk

    I attempted the upgrade this morning and can confirm that it no longer crashes the website upon update 🙂

    Thanks again! I’ll make this as resolved. Take care

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Fatal 500 error when upgrading plugin to v1.17.6’ is closed to new replies.