• Resolved Sean Conklin

    (@seanconklin)


    Uncaught Error: Failed opening required ‘/nas/content/live/codedcommerce/wp-content/plugins/godaddy-payments/vendor/composer/platform_check.php’ (include_path=’.:/usr/share/pear/php:/usr/share/php’) in /nas/content/live/codedcommerce/wp-content/plugins/godaddy-payments/vendor/composer/autoload_real.php:25 Stack trace: #0 /nas/content/live/codedcommerce/wp-content/plugins/godaddy-payments/vendor/autoload.php(7): ComposerAutoloaderInit3fb05797026c18af4559e5e459e1ddca::getLoader() #1 /nas/content/live/codedcommerce/wp-content/plugins/godaddy-payments/godaddy-payments.php(105): require_once(‘/nas/content/li…’) #2 /nas/content/live/codedcommerce/wp-includes/class-wp-hook.php(308): GD_Poynt_For_WooCommerce_Loader->initPlugin(”) #3 /nas/content/live/codedcommerce/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array) #4 /nas/content/live/codedcommerce/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #5 /nas/content/live/codedcommerce/wp-settings.php(480): do_action(‘plugins_loaded’) #6 /nas/content/live/codedcommerce/wp-config.php(67): require_once(‘/nas/content/li…’) #7 /nas/content/live/codedcommerce/wp-load.php(50): require_once(‘/nas/content/li…’) #8 /nas/content/live/codedcommerce/wp-admin/admin.php(34): require_once(‘/nas/content/li…’) #9 {main} thrown in /nas/content/live/codedcommerce/wp-content/plugins/godaddy-payments/vendor/composer/autoload_real.php on line 25

Viewing 6 replies - 1 through 6 (of 6 total)
  • Upgrade to v1.4.0 caused PHP Fatal error. Had to disable the plugin. Divi site running PHP 8.1. Thank you   
    
    [02-Feb-2023 15:54:45 UTC] PHP Fatal error: Uncaught Error: Failed opening required '/home/'redacted'/public_html/wp-content/plugins/godaddy-payments/vendor/composer/platform_check.php' (include_path='.:/opt/cpanel/ea-php81/root/usr/share/pear') in /home/'redacted'/public_html/wp-content/plugins/godaddy-payments/vendor/composer/autoload_real.php:25
    Stack trace:
    
    0 /home/'redacted'/public_html/wp-content/plugins/godaddy-payments/vendor/autoload.php(7): ComposerAutoloaderInit3fb05797026c18af4559e5e459e1ddca::getLoader()
    
    1 /home/'redacted'/public_html/wp-content/plugins/godaddy-payments/godaddy-payments.php(105): require_once('/home/'redacted'/…')
    
    2 /home/'redacted'/public_html/wp-includes/class-wp-hook.php(308): GD_Poynt_For_WooCommerce_Loader->initPlugin('')
    
    3 /home/'redacted'/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)
    
    4 /home/'redacted'/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
    
    5 /home/'redacted'/public_html/wp-settings.php(480): do_action('plugins_loaded')
    
    6 /home/'redacted'/public_html/wp-config.php(119): require_once('/home/'redacted'/…')
    
    7 /home/'redacted'/public_html/wp-load.php(50): require_once('/home/'redacted'/…')
    
    8 /home/'redacted'/public_html/wp-admin/admin.php(34): require_once('/home/'redacted'/…')
    
    9 /home/'redacted'/public_html/wp-admin/index.php(10): require_once('/home/'redacted'/…')
    
    10 {main}
    
    thrown in /home/'redacted'/public_html/wp-content/plugins/godaddy-payments/vendor/composer/autoload_real.php on line 25

    You need to 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 Sean Conklin

    (@seanconklin)

    Right, use backups, WP-CLI, or the interface to download the v1.3.4 here https://www.ads-software.com/plugins/godaddy-payments/advanced/ scroll down to the drop-down menu at the bottom and pick version 1.3.4

    I use the backup service at winhost. It’s part of the dropmysite software. Works great and I was able to restore in about 30 seconds. Saved my ass today because I was running a special and had people buying on the site. I find it very troubling that GoDaddy didn’t test this plugin out before pushing it to WP. I have 5 sites that use GD Payments and they all failed on this new update.

    There’s a new update that resolves the error. It’s 1.4.1

    Plugin Support ryanskyverge

    (@ryanskyverge)

    @seanconklin @eric4 @presson2022
    Thanks for letting us know about this issue. Yes, as @presson2022 has mentioned v1.4.1 has been released and resolves the error.

    I’m very sorry for the disruption this had on your business. We are doing a root cause investigation to ensure we have the necessary checks in place to ensure this doesn’t repeat.

    I’ll mark this thread as resolved, but don’t hesitate to let us know if anything else comes up.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘PHP Fatal Error upgrading to v1.4.0’ is closed to new replies.