• Resolved k9essentials

    (@k9essentials)


    I updated the eway plugin and my site went down with a critical error. Not just this site but 2 others as well, using various plugins which I have systematically tried disabling to find a conflict. It appears the eway plugin is the issue.

    I rolled back to the previous version and the site was back online and working fine.

    Has anyone else had this issue? Maybe found a solution?

    • This topic was modified 3 years, 6 months ago by k9essentials.

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

Viewing 11 replies - 1 through 11 (of 11 total)
  • I have had the same thing happen on my website when i updated the eway plugin today 15/5/21.
    I had to deactivate the plugin to get my site working again.

    I am surprised no one else has had these issues. I have been trying to work out what the problem is – but afraid to try and update it again – as it crashed my site twice already.
    Hoping someone can get back to -us – about this

    https://www.bambinomanly.com.au

    Maybe it is storefront and eway – looks like k9essentials is having the same issues.
    What PHP version are you running? Apparantly my site is running at 7.2.34 but needs to be at 7.4?

    +1 for a site down because of this update. Error log shows:
    [14-May-2021 17:05:38 UTC] PHP Parse error: syntax error, unexpected ')' in /home/privateinfo/public_html/wp-content/plugins/woocommerce-gateway-eway/includes/class-wc-gateway-eway-blocks-support.php on line 66

    Granted, it is on a site lagging behind on WC 4.7.1. I guess I’ll be updating that ASAP.

    Rolled back to 3.1.25 and all is well until I can get to it.

    • This reply was modified 3 years, 6 months ago by Pt. Reason: Added more info

    Yes I had this issue and needed to rollback in cpanel as the critical issues obvs take down the site. I will be staying with 3.1.25 until more info is known or a fix/update is found for this issue with 3.2.0.

    The 3.2 plugin is also crashing a client site for me. I have gotten the critical error. I have tried disabling all other themes and plugins and it’s definitely this one. I am going to roll back to the old version for now.

    For anyone else who has this error and is a tinkerer like me-and unsure what to do:-. Download “rollback” plugin to your website from woo commerce which adds for you the option to go back (rollback) to an earlier version of a problematic plug-in

    Plugin Support Aashik P – a11n

    (@aashik)

    Hi there!

    Interestingly, I could not replicate the same error on my own test site, even on WooCommerce 4.7. I’ve tried both PHP 7.3 and 7.4 versions so far.

    If you update your PHP to either of the versions and still see the same error, could you please share a copy of your site’s System Status? You can find it via WooCommerce > Status. Select “Get system report” and then “Copy for support”.? Once you’ve done that, paste it here in your response.

    cc @coffeecup22 @cocobails @reneegoodog @bncpeter @k9essentials

    EDIT: Please do note that I only tested this on Sandbox mode. Can you please also cross-check if the behavior is only seen on Live mode?

    You can set up a staging site to test by getting in touch with your web host, or using a plugin. The WP Staging plugin is perfect for making a clone of your live site so you can set up a local development site. If you need help setting it up, you can find the step by step documentation here: https://www.ads-software.com/plugins/wp-staging/#description under “HOW TO INSTALL AND SETUP?”

    • This reply was modified 3 years, 6 months ago by Aashik P - a11n. Reason: Added sandbox details

    I’m seeing the error in PHP 7.2.34 also. It’s because you’re using a trailing comma at the end of the argument list, which is only supported in PHP 7.3 upwards:


    /* translators: 1 is the expiration month and 2 the expiration year */
    ‘expires’ => sprintf(
    esc_html__( ‘%1$s/%2$s’, ‘wc-eway’ ),
    $saved_card[‘exp_month’],
    $saved_card[‘exp_year’],
    ),

    Removing the trailing comma (or upgrading PHP to 7.3) fixes the error.

    • This reply was modified 3 years, 6 months ago by globalmatt.
    Plugin Support Aashik P – a11n

    (@aashik)

    @globalmatt Thank you for clarifying.

    PHP 7.2 is no longer supported by php.net as it has reached its end of life. For anyone using that, we strongly recommend updating to PHP 7.3 or above, as recommended by WooCommerce (Server Recommendations).

    I can’t make any promises, but I’ve gone ahead and flagged this to the developers to see if they’re planning to make the extension work with PHP 7.2 as well.

    Thank you for the pointer on the problem. That’s very helpful.

    A fix has been released. Please update to 3.2.1 to avoid the fatal error.

    Plugin Support Aashik P – a11n

    (@aashik)

    Thank you, @shendz.

    I’ll mark this topic as solved for now. Please feel free to open a new topic if you have any other questions.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Eway 3.2 update crashing site’ is closed to new replies.