Fatal error with recent update

  • Resolved hswebmaster

    (@hswebmaster)


    7 years, 8 months ago

    Hello,
    I recently updated your plugin on a new site I’ve been working on and it returns this error now on every page:

    Fatal error: Can’t use method return value in write context in /home/genshai/public_html/wp-content/plugins/woocommerce-gateway-stripe/includes/class-wc-gateway-stripe.php on line 267

    Only way to restore the site is to delete the plugin folder via FTP. I did not have this issue with any previous version and now am concerned about updating it on other sites I use this plugin on. Please advise.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support John Coy a11n

    (@johndcoy)

    Automattic Happiness Engineer

    7 years, 8 months ago

    Hi @hswebmaster

    Oh no! This is likely an issue with the active theme overriding WooCommerce templates or another plugin.

    As a first step, could you try switching back to a default theme like Twenty Seventeen and disabling all plugins except for WooCommerce and Stripe to see if this resolves the issue? If so, then re-enable each one at a time until you find the one that’s causing the conflict.

    Thread Starter hswebmaster

    (@hswebmaster)

    7 years, 8 months ago

    Hi John,
    That’s some impressive response time! Thank you for the direction. I have done as you suggested – deactivate all but WooCommerce plugins and switched to Twenty Seventeen Theme but as soon as I go to activate Stripe it returns the same Fatal Error. I’m afraid it does not appear to be an issue with my theme or other plugins. What PHP version is recommended for this?

    Plugin Support John Coy a11n

    (@johndcoy)

    Automattic Happiness Engineer

    7 years, 8 months ago

    Hi @hswebmaster

    PHP 5.6 or later is required.

    https://github.com/woocommerce/woocommerce-gateway-stripe

    Thread Starter hswebmaster

    (@hswebmaster)

    7 years, 8 months ago

    Thanks that seemed to fix it. Was running 5.4 by default.

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

The topic ‘Fatal error with recent update’ is closed to new replies.