robertstaddon
Forum Replies Created
-
Thank you for taking the time to explain your position, @inpsydekrystian . What is your process for determining how widespread an issue is and whether it is critical enough that you should push a release?
It is an unfortunate position that you’ve placed those of us who are experiencing this “non-urgent” issue of PHP fatal errors from your plugin blocking customer payments. It doesn’t appear that we can install your 3.1.1 fix to “the critical issue that required immediate action” without recreating fatal errors that block customer payments.
So because your fix for this bug was not in your 3.1.1 release, your 3.1.1 release overwrote the 3.1.0 patched code that was installed on live websites and started re-causing fatal errors on live stores. It is incredibly frustrating and difficult to work with your plugin’s system of patching code without dot releases and then overwriting it in dot releases with “more widespread” issues.
I would suggest that you follow the simple and straightforward approach that the official WooCommerce software takes (such as with today’s 10.2.2 bug fix) and release dot releases that fixes fatal errors in your plugin even if they aren’t “widespread”. I do not believe it to be an industry-standard best practice for a plugin developer to release patches to fatal errors without a dot release and then allow those patches to be overwritten by new dot releases that don’t have the patches applied.
@inpsydekrystian Releasing a 3.1.0.1 version with the patch would be a simple way to avoid all of these continuing, completely avoidable problems for your plugin users. Releasing a new patched dot release is the usual way that plugin developers resolve bugs that are causing fatal errors on user’s websites.
Hello Krystian, thank you for your work on this! I’ve downloaded the fixed package and will test it out.
Wouldn’t it be a good idea to release the fixed package as 3.1.0.1 so that we could make sure the code that doesn’t cause a fatal error gets pushed out to everyone?
Forum: Plugins
In reply to: [WooCommerce Tax (formerly WooCommerce Shipping & Tax)] 3.0.6 breaks installSame fatal error!
[21-Jul-2025 13:12:22 UTC] PHP Fatal error: Uncaught Error: Failed opening required ‘/public_html/wp-content/plugins/woocommerce-services/src/StoreNotices/StoreNoticesNotifier.php’ (include_path=’.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php’) in /public_html/wp-content/plugins/woocommerce-services/vendor/jetpack-autoloader/class-php-autoloader.php:102
Stack trace: 0 /public_html/wp-content/plugins/woocommerce-services/woocommerce-services.php(876): Automattic\Jetpack\Autoloader\jp7109386222804879fea6838ada605690\al5_0_7\PHP_Autoloader::load_class() 1 /public_html/wp-content/plugins/woocommerce-services/woocommerce-services.php(734): WC_Connect_Loader->load_dependencies()
2 /public_html/wp-includes/class-wp-hook.php(324): WC_Connect_Loader->pre_wc_init()
3 /public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
4 /public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
5 /public_html/wp-content/plugins/woocommerce/includes/class-woocommerce.php(851): do_action()
6 /public_html/wp-includes/class-wp-hook.php(324): WooCommerce->init()
7 /public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
8 /public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
9 /public_html/wp-settings.php(727): do_action()
10 /public_html/wp-config.php(106): require_once(‘/public_html…’)
11 /public_html/wp-load.php(50): require_once(‘/public_html…’)
12 /public_html/wp-blog-header.php(13): require_once(‘/public_html…’)
13 /public_html/index.php(17): require(‘/public_html…’)
14 {main}thrown in /public_html/wp-content/plugins/woocommerce-services/vendor/jetpack-autoloader/class-php-autoloader.php on line 102
Forum: Plugins
In reply to: [LiteSpeed Cache] The latest update made my sites too slowGood news! After updating all sites to 7.0.0.1-rc1 through the Toolbox master branch, my slowness disappeared and after about an hour the “LiteSpeed Cache CDN” settings page started functioning normally and the “429 Too Many Requests” errors stopped occuring.
Forum: Plugins
In reply to: [LiteSpeed Cache] The latest update made my sites too slowAfter installing Query Monitor on the site, I’m seeing an error message being returned from the API call to https://api.cloudflare.com/client/v4/zones “429 Too Many Requests”. It may be that the initial bug in 7.0 triggered way too many API calls that exceeded CloudFlare’s limits and is now stopping any of my sites from connecting to CloudFlare. I’m going to try updating every site to 7.0.0.1 and then see if this “420 Too Many Requests” errors will eventually go away.
I noticed that a new version of the plugin was just released! Did this new version patch this bug that breaks Smart Coupons for WooCommerce?
Thank you!
The message does only appear when someone is logged into the store. But it appears for everyone logged into the store with any role, whether they have a saved payment method or not. This may be a bug in WooCommerce, but it only happens when your plugin is enabled, even with all payment methods turned off.
This bug is simple to reproduce:
- Install WooCommerce 9.7 and this plugin (v. 3.3.82)
- Connect this plugin to a Stripe account (or if you don’t want to do that, enable any offline payment method such as Direct bank transfer, Check payments, or Cash on delivery).
- Create a simple product and go to the Checkout page (logged in as any user with any role). An odd and unnecessary “Use another payment method” message will appear direcctly under “Payment options”.
I have a demo site set up if you’d like a login to it.
Forum: Plugins
In reply to: [G-Forms hCaptcha] Is it alive?I don’t think this plugin is supported any more. You may want to switch over to this plugin that is maintained by hCaptcha and includes support for Gravity Forms: https://ww.wp.xz.cn/plugins/hcaptcha-for-forms-and-more/
Forum: Plugins
In reply to: [Login for Google Apps] Fatal Error on “Edit User” Page in New 3.5 UpdateThank you! Your new version resolved the issue.
Forum: Plugins
In reply to: [WooCommerce Shipping] Can’t Reprint Shipping LabelsThis is great news! Thank you!!
Forum: Plugins
In reply to: [Code Snippets] Premium: Code vault connected, but suddenly emptyI recently started experiencing the exact same issue across many different websites.
Forum: Plugins
In reply to: [Login for Google Apps] Plugin Abandoned?That would be wonderful @slaffik ! I really like your plugin.