stepfaul
Forum Replies Created
-
Forum: Themes and Templates
In reply to: [Storefront] Adding &display=swap to Google FontsThanks @riaanknoetze for your reply. I will submit an idea as you suggest.
Hi did you ever resolve this issue. We are seeing the same even with all plugins disabled??
Thanks ??
No I did not. To be honest I tried rolling back versions of Stripe and WooCommerce, disabling Varnish my server based cache (and also disabling WordPress cache for css as well) and disabling all plug-ins leaving just WooCommerce and Stripe along with the StoreFront theme and the issue still occurred.
As mentioned earlier I not too fussed about this feature, although it is a nice to have it is not worth my time in troubleshooting and raising support tickets just trying to get it working.
One thing for sure is that it was working, and after updating either WooCoomerce or Stripe or both it stopped working. Other things may have updated behind the scenes but from my perspective it was a couple of plug-in updates and ‘boom’ things broke.
Forum: Plugins
In reply to: [WooCommerce] WooCommerce update to 4.0.1This is resolved now.
Turns out that during the upgrade something occurred which broke the Action Scheduler. I could see that the Action Scheduler was constantly in a migration in progress state.
To resolve I went to the database and deleted the wp_actionscheduler tables (there were three or four). After I browsed to WooCommerce > Status > Tools and manually ran the Update database option which seemed to resolve the issue.
More details can be found in this post – https://www.ads-software.com/support/topic/action-scheduler-migration-in-progress-the-list-of-scheduled-actions-may-be-inc-2/#post-12693028
@benoitfouc Great, thanks for replying so quickly!
This looks to have worked as things were a bit of a mess after the DB upgrade.
Stay safe and thank you.
- This reply was modified 4 years, 11 months ago by stepfaul.
Good morning @benoitfouc
I am experiencing what looks to be the same issue. Can I ask if you did anything else after deleting the actionschedular tables?
I am trying to establish if after deleting the tables I need to perform other actions for WooCommerce to recreate them. Or does WooCommerce simply recreate them automatically?
Many thanks
Steve.
Forum: Plugins
In reply to: [WooCommerce] WooCommerce update to 4.0.1I do also recall seeing a message during the DB upgrade about missing tables and an attempt to recreate possibly??
I have managed to access to logs on the system page by appending &tab=log to the status page url. I am unable to access the System status tab still. I can see the most recent error in the logs:
2020-04-17T18:47:10+00:00 CRITICAL Uncaught Error: Undefined class constant ‘QUEUE_GROUP’ in /var/www/littletigergifts.co.uk/wp-content/plugins/woocommerce/packages/woocommerce-admin/includes/wc-admin-update-functions.php:70
Stack trace:
#0 /var/www/littletigergifts.co.uk/wp-content/plugins/woocommerce/includes/class-wc-install.php(223): wc_admin_update_0251_remove_unsnooze_action()
#1 /var/www/littletigergifts.co.uk/wp-includes/class-wp-hook.php(287): WC_Install::run_update_callback(‘wc_admin_update…’)
#2 /var/www/littletigergifts.co.uk/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(”, Array)
#3 /var/www/littletigergifts.co.uk/wp-includes/plugin.php(544): WP_Hook->do_action(Array)
#4 /var/www/littletigergifts.co.uk/wp-content/plugins/woocommerce/packages/action-scheduler/classes/actions/ActionScheduler_Action.php(22): do_action_ref_array(‘woocommerce_run…’, Array)
#5 /var/www/littletigergifts.co.uk/wp-content/plugins/woocommerce/packages/action-scheduler/classes/abstracts/ActionScheduler_Abstract_QueueRunner.php(65): ActionSc in /var/www/littletigergifts.co.uk/wp-content/plugins/woocommerce/packages/woocommerce-admin/includes/wc-admin-update-functions.php on line 70- This reply was modified 4 years, 11 months ago by stepfaul.
Just to chip in I did contact my hosting company re the Varnish 503 error and they came back with the following response:
Requests containing ?wc-ajax have been bypassed already,
The varnish 503 means that the PHP behind the request is failing, rather than an issue with Varnish itself. It’s likely a PHP or WordPress error.The Varnish cache was disabled and the error still occurred but has since been re-enabled for my staging site. I was unable to investigate any further as I only have an iPhone\iPad which to my knowledge has limited browser developer tools (as far as I could see anyway).
Steve.
Thanks for taking the time to look at this @wbrubaker,
I had not even thought of firing up the developer tools to troubleshoot this as it was seemingly a plugin issue.
I will have a chat to my hosting provider who manage the Varnish cache to take a look.
Kind regards
Steve.
- This reply was modified 5 years ago by stepfaul.
Thanks @wbrubaker as stated in an earlier reply I have already tried what you have suggested with no success.
In addition to this I have just re-tested after upgrading my staging site to WooCommerce 4.01 and clearing all caches. Again I find I encounter the same issue.
Theme wise I am running the latest StoreFront theme but have also tried with Twenty Twenty as well.
Steve.
Forum: Plugins
In reply to: [WooCommerce] Warning to “Deactivate old WooCommerce Admin versionHi All,
WooCommerce Admin is now part of WooCommerce core so no additional plugins are required for this functionality.
It seems like you still have the now out of date WooCommerce Admin plugin and have WooCommerce 4.0 installed which includes the plugin feature as part of the core.
I would suggest removing the WooCommerce Admin plugin completely as you no longer need it. This should stop the message from being displayed as the separate plugin is no longer being updated.
As standard I would suggest you back up site and DB before you go changing things
Steve.
- This reply was modified 5 years ago by stepfaul.
I just tested disabling all plugins on my staging site and just left StoreFront theme, WooCommerce and Stripe plugins activated and after clearing all caches the shipping error is still displayed.
It would seem the issue is not down to a plugin conflict.
Steve.
Hi @gibbo78
I still get the same issue on my staging site which is running the latest versions of Stripe and WooCommerce. The iPhone I tested on is also running the latest iOS.
I have still not had the chance to raise a support ticket. In the meantime I have added the following to my functions.php to hide the button on my live site:
/* Remove Stripe Apple Pay button on single product pages as error with delivery address being wrong when trying to purchase */ add_filter( 'wc_stripe_hide_payment_request_on_product_page', '__return_true' );
Steve.
- This reply was modified 5 years ago by stepfaul.
Hi @stepfaul,
Did the Apple Pay configuration work for you? Because on my site I do not understand why it does not work. I present the problem here: https://www.ads-software.com/support/topic/problem-with-adding-apple-pay/.
Can you just watch and tell me what you think about it?
Looking forward to your return.
Regards,
Sorry I did not reply but I have been very busy. I cannot answer your questions re Stripe integration as I set my site up with Stripe around 5, maybe 6 years ago as we were one of the early WooCommerce adopters and did not encounter any issues back then if I recall correctly. I can’t even remember what steps I took to configure stripe as it was such a long time ago.
In addition to this I don’t provide support for Stripe, WordPress or WooCommerce either.
It might be best if you raise a support ticket with WooCommerce directly for the quickest answer. This is something that I intend to do when I have a moment but for my issue I have simply disabled the troublesome button as I am not in any rush. I was hoping that the issue might have been a known one and I might have received an answer quickly but this does not seem to be the case!
@rogercoathup Thanks for the info. I just rolled back Stripe to v4.2.5 which is 4 versions old but the issue still persists. I suspect as you say it might be something to do with WooCommerce which I am not in a position to rollback versions.
Thanks @psealock,
Clearing the browser cache appears to have done the trick. Earlier I did clear the WP cache and refresh the browser but that can’t have been enough.
Thanks all for your time.
Steve.