• Resolved ttoaster

    (@ttoaster)


    Hi,

    Just updated the plugin to 3.5.0 and was informed of the following error:

    Your Site is Experiencing a Technical Issue

    WordPress version 6.1.1
    Current plugin: WooCommerce Square (version 3.5.0)
    PHP version 7.4.3

    Error Details
    =============
    An error of type E_ERROR was caused in line 12 of the file /var/www/shop/wp-content/plugins/woocommerce-square/vendor/square/square/src/ConfigurationInterface.php. Error message: Uncaught Error: Interface ‘CoreInterfaces\Http\HttpConfigurations’ not found in /var/www/shop/wp-content/plugins/woocommerce-square/vendor/square/square/src/ConfigurationInterface.php:12

Viewing 15 replies - 16 through 30 (of 37 total)
  • I’ve experienced this issue on my site as well, using Elementor and Hello theme. As soon as I deactivate the plugin, the error goes away. What has everyone done to resolve this? It’s critical that we use Square for checkout. Thanks.

    Thread Starter ttoaster

    (@ttoaster)

    @edisonapps do like most of us that have had the issue, roll back to the previous version, or if you want a more reliable plugin look elsewhere…

    Otherwise, ditch Square and use Stripe instead; which I think I’m just about to do (ditch Square; I already use Stripe), as the level of support for this plugin is frankly unacceptable!

    @ttoaster how did you roll back the plugin?

    Thread Starter ttoaster

    (@ttoaster)

    @edisonapps I used the Rollback plugin… but you can simply download the old version from the Plugin page and then re-install it manually, if you prefer…

    I never installed 3.5.0 on my Production site because of the issue I reported when testing it on my Dev server (which is a duplicate of the Prod server).

    I rolled back and it works again. BS responses from the plugin author!

    Obviously, I’m not the only person having this issue (on every client’s site who uses Square) and it’s disheartening to see that it was reported 6 days ago but no fix seems eminent. I need to access a copy of the previous version ASAP before my clients revolt.

    This WP Rollback plug-in worked for me to roll it back to the previous version 3.4.2. I agree with you that Automattic should have fixed this issue before now! https://www.ads-software.com/plugins/wp-rollback/

    Plugin Support Kaushik S. a11n

    (@kaushiksomaiya)

    Hi there @ttoaster

    This appears to be an upgrade issue, and our developers are looking into it currently.

    Some of our users reported this was a one-off error on upgrading, however if you’re seeing the issue after updating, I’d suggest staying on version 3.4.2.

    I am not sure when a fix would be released but I’d suggest keeping an eye on the changelog for updates.

    @edisonapps The error that you’ve reported is a bit different and is related to outdated WooCommerce Subscriptions plugin. You’ll need to update it to the latest version to fix that.

    I hope this helps!

    Thread Starter ttoaster

    (@ttoaster)

    This issue is still not fixed in 3.6.0, just updated from 3.4.2 and yet again I get the error email, and in it is the very same error message. Can you not fix this? I’m not the only one having this issue!

    Same critical error in 3.6.0. Rolled back again to version 3.4.2.

    Hi @ttoaster @proteanstar

    Thanks for your confirmation that the error still persists even after updating to version 3.6.0.

    I checked the changelog, and confirmed that version 3.6.1 is already available which fixed the fatal error on PHP 8 caused while importing products.

    Can you please give it a try and see if this resolves the issue here?

    Thread Starter ttoaster

    (@ttoaster)

    Hi,

    3.6.1 doesn’t throw the error I reported with 3.5.0 and 3.6.0; however I have PHP 7.4 (not 8.0) so there are some other code changes in 3.6.1 than just the PHP 8.0 fix!

    I will do some more testing with this version on my dev servers before I update my prod servers, and see if there are any other issues.

    Hi @ttoaster

    3.6.1 doesn’t throw the error I reported with 3.5.0 and 3.6.0; however I have PHP 7.4 (not 8.0) so there are some other code changes in 3.6.1 than just the PHP 8.0 fix!

    I’m glad that updating to the latest release fixed your issue here. ??

    I will do some more testing with this version on my dev servers before I update my prod servers, and see if there are any other issues.

    Let us know how the testing goes!

    I looked at the current critical error and the other ones from the past month, crashing my site each time I tried to upgrade the WooCommerce Square plugin from 3.4.2 to 3.5.0, rolled it back to 3.4.2., worked again, then tried to upgrade from 3.4.2 to 3.6.0, same error, rolled it back again to 3.4.2, then tried to upgrade from 3.4.2 to 3.6.1, same error, rolled it back again to 3.4.2. Then unactivated Extendify. Please note that the WooCommerce Square plugin crashed my site every time, with the previous version of Extendify, as well as the current version 1.3.0, updated two weeks ago.

    I was able to upgrade WooCommerce Square plugin from 3.4.2 to version 3.6.1, however: This thread should not be marked as solved. There is a conflict between Extendify and WooCommerce Square plugin.

    I looked at the current critical error and the other ones from the past month, crashing my site each time I tried to upgrade the WooCommerce Square plugin from 3.4.2 to 3.5.0, rolled it back to 3.4.2., worked again, then tried to upgrade from 3.4.2 to 3.6.0, same error, rolled it back again to 3.4.2, then tried to upgrade from 3.4.2 to 3.6.1, same error, rolled it back again to 3.4.2. Then unactivated Extendify. https://www.ads-software.com/plugins/extendify/ Please note that the WooCommerce Square plugin crashed my site every time, with the previous version of Extendify, as well as the current version 1.3.0, updated two weeks ago.

    I was able to upgrade WooCommerce Square plugin from 3.4.2 to version 3.6.1, however: This thread should not be marked as solved. There is a conflict between Extendify and WooCommerce Square plugin.

Viewing 15 replies - 16 through 30 (of 37 total)
  • The topic ‘3.5.0 Error’ is closed to new replies.