• Resolved gwronkowski

    (@gwronkowski)


    I am using version 2.6.65 of plugin.
    I have an error at checkout seen in javascript console:

    /checkout/?wc-ajax=checkout:1 Failed to load resource: the server responded with a status of 500 (Internal Server Error)

    I have checked plugin log entries: Log entries success. Can’t see any problems here.

    My localhost server php.log containes:

    Stack trace:
    #0 C:\laragon\www\hdri-skies\wp-includes\class-wp-hook.php(286): WC_Braintree_Payment_Gateway::maybe_update_order_status('processing', 315079)
    #1 C:\laragon\www\hdri-skies\wp-includes\plugin.php(203): WP_Hook->apply_filters('processing', Array)
    #2 C:\laragon\www\hdri-skies\wp-content\plugins\woocommerce\includes\abstracts\abstract-wc-order.php(2313): apply_filters('woocommerce_pay...', 'processing', 315079)
    #3 C:\laragon\www\hdri-skies\wp-content\plugins\woo-payment-gateway\includes\class-wc-braintree-gateway.php(285): WC_Abstract_Order->payment_complete('j6fqsh2k')
    #4 C:\laragon\www\hdri-skies\wp-includes\class-wp-hook.php(286): WC_Braintree_Payment_Gateway->process_o in C:\laragon\www\hdri-skies\wp-content\plugins\woo-payment-gateway\includes\class-wc-braintree-gateway.php on line 1008

    What can be a problem ?

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Clayton R

    (@mrclayton)

    Hi @gwronkowski,

    To start, you should upgrade to version 3.1.0 of the plugin. Version 2.6.65 is very old. Can you please upgrade and then test again?

    Is that the full stack trace?

    Thanks,

    Thread Starter gwronkowski

    (@gwronkowski)

    No I can’t. I am running WordPress 4.9.8 and WooCommerce 2.4.12. This is the latest version of plugin which seems to work still. Upgrading is very costly as we have complex configuration and overwrites. Last time it was upgraded 1 year ago and it was very hard and long job. We prefer to stay at this release at the moment.

    • This reply was modified 6 years, 5 months ago by gwronkowski.
    Plugin Author Clayton R

    (@mrclayton)

    @gwronkowski,

    Ya any version of the plugin 3.0.0+ only supports WC 3.0.0 since that’s over 2 years old. Can you please reach out to our support email and send me a zip of the 2.6.65 version you are using?

    Also, your stack trace should have a more descriptive message like “null exception thrown on line 155” as an example. Your stack trace seems to be summarized. Go in to the WP Admin and click WooCommerce > Status > Logs and you should be able to find an error log with more details.

    Thanks,

    Thread Starter gwronkowski

    (@gwronkowski)

    Latest version of plugin gives me an error:
    Fatal error: Class 'WC_Payment_Token' not found in \wp-content\plugins\woo-payment-gateway\includes\abstract\abstract-class-wc-payment-token-braintree.php on line 11

    • This reply was modified 6 years, 5 months ago by gwronkowski.
    Plugin Author Clayton R

    (@mrclayton)

    @gwronkowski,

    Did you read my last reply? Any version of our plugin over 3.0.0+ only supports WC version 3.0.0+

    You’re getting that error because your version of WC is 2.4.12 and WC added a lot of features in the last few years.

    Thanks,

    Thread Starter gwronkowski

    (@gwronkowski)

    I have downloaded this from here:
    https://pl.ww.wp.xz.cn/plugins/woo-payment-gateway/advanced/
    Just scroll to bottom of page and choose 2.6.65

    Thread Starter gwronkowski

    (@gwronkowski)

    We have now debate with owner of store, looks like last developer who had to upgrade woocommerce to latest version left old version. Thanks for clearing up.

    Plugin Author Clayton R

    (@mrclayton)

    @gwronkowski so the store owner has agreed to upgrade WC to the latest version?

    Thanks,

    Thread Starter gwronkowski

    (@gwronkowski)

    Yes she now understands that without total upgrade many other plugins won’t work properly and it has no sense to maintain old code. Thanks for quick response!

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

The topic ‘500 ajax error’ is closed to new replies.