Critical error in plugin 1.4.0

  • Resolved vuzu177

    (@vuzu177)


    2 years, 1 month ago

    GoDaddy Payments plugin is causing a critical error (white screen at the homepage) for a client’s website. When turned off, the site functions again. Running debug mode and getting this error (I’ve X’d out some directory info):

    eb-2023 16:10:44 UTC] PHP Warning: ?require(/home/XXXXXXX.cloudwaysapps.com/XXXXXXX/public_html/wp-content/plugins/godaddy-payments/vendor/composer/platform_check.php): failed to open stream: No such file or directory in /home/XXXXXXX.cloudwaysapps.com/XXXXXXX/public_html/wp-content/plugins/godaddy-payments/vendor/composer/autoload_real.php on line 25

    Can someone assist with this issue?

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

  • Restore to the previous version. That’s what i had to do. This new update is broken. I backup every day so I hope you did to so just restore previous version. To bypass the error on site, go to file manager and rename the godaddypayments folder to something else. That will deactivate it and you can get your site up again while you restore backup.

    Thread Starter vuzu177

    (@vuzu177)

    @presson2022 thanks! I was able to restore to a previous version. Backups are a lifesaver. I also disabled auto-updates to prevent the plugin from updating to the broken version.

    As a rule I use a test site that is a mirror of what I have for my main site and I usually update there first but today I didn’t and boy was that a mistake. Granted I got back up in under a minute it sure reinstated the fact that I need to keep updating on test site first and yes, backups are lifesavers!

    Plugin Support ryanskyverge

    (@ryanskyverge)

    @vuzu177 Thanks for reporting this issue. I’m very sorry for the impact this had on your business.

    We have released v1.4.1 of the plugin which resolves this issue. I’ll mark this thread as “resolved” but please don’t hesitate to let us know if anything else comes up.

    Thread Starter vuzu177

    (@vuzu177)

    @ryanskyverge The updated version seems to be working well. And thanks for having the problem resolved so quickly!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Critical error in plugin 1.4.0’ is closed to new replies.