bbceg
Forum Replies Created
-
Great, thanks for the update.
Hi @duracelltomi ,
I can confirm that this issue occurs in both Chrome & Firefox on Windows 10 but not in Edge. Any ideas when the latest version will be out of beta?
Thanks
Thanks @nicw that’s been done. I’ll leave this thread open for now in case we can supply a resolution for anyone else coming across this issue in the future.
Hi @simplysaru
Thanks for the response. There are no errors showing in the error log around the time of the first Stripe log entry. The NGINX access log does show more than 6500 entries similar to this one in a sub 30 minute window:
{STRIPE IP} - - [05/Jul/2021:07:17:50 +0100] "POST /?wc-api=wc_stripe HTTP/1.1" 200 5 "-" "Stripe/1.0 (+https://stripe.com/docs/webhooks)"The first 450 succeeded before the web server was overwhelmed (after 3 minutes or so) and then the response code changed as the requests timed out or errored.
Any additional thoughts welcome.
Thanks @wbrubaker. Any ideas how the problem would have manifested itself and where it may have originated from?
Incidentally, deleting the webhook and recreating it did appear to prevent the remaining requests from firing (they were due at 03:30 UTC and there are no corresponding entries in the NGINX access log). Any ideas why that would be?
I wasn’t looking for the check to go away, merely a way to accept responsibility for the environment and override the behaviour. I can see how this is probably not very progressive so will bow out and find a new way forward.
Thanks for the swift response @macmanx, that makes sense. I suppose it might have been an option to allow hosts / website owners to accept their version of PHP, even if via a filter.
As mentioned above, there would seem to be good reasons to stay with a distro’s packages and in my specific case I would feel confident that the Ubuntu team will keep the currently maintained PHP version secure.
I can see there is a filter ‘wp_is_php_version_acceptable’ but this is only available to make the check more strict. With the above in mind do you think it would make sense to remove this restriction?
Forum: Plugins
In reply to: [Schema] class-oembed.php is deprecatedUpdated to WordPress 5.7.1 and the error disappeared…
Forum: Plugins
In reply to: [WooCommerce] Analytics > Settings Page Blank after UpdateI can confirm that fixes it for me.
Forum: Plugins
In reply to: [WooCommerce] Analytics > Settings Page Blank after UpdateHi @fylgjur
My original tests were carried out in Chrome. Since your message I’ve tried in Edge (in-private) with the same result. I’ve deleted and reinstalled but again no change.
nginx v1.14.0
PHP (FPM) 7.2.24Let me know if there is anything else I can provide to help troubleshoot.
Forum: Plugins
In reply to: [WooCommerce] Analytics > Settings Page Blank after UpdateI’m seeing the exact same behaviour.
I’ve tested with a vanilla WordPress install with only Woocommerce (v5.1.0) active. I can confirm I do not see any errors when the WordPress version is 5.6.2. On upgrading to WordPress 5.7 the page is blank and the React errors appear (I believe they suggest an infinite loop).
Thanks @karesz that is indeed useful.
@wooassist assuming you still can’t replicate, might you consider applying the fixes anyway and then seeing if anything is affected? I know this might seem a little backwards but it would be easy to rollback the changes if you had to. Just a thought.Hi @karesz ,
Thanks for putting that together, they look like what I had (though they’ve all been lost since the last update). Are you reapplying each time or is there a better way I’m missing?Hi @wooassist
Any update on this issue? I’m having to reapply the fixes every time a plugin update is released. Once again, I’m more than happy to list the fixes if required.
ThanksForum: Plugins
In reply to: [Flamingo] Date changes when moving an email from inbox to spamApologies, this problem is likely to be specific to the website in question as I’ve just tested a different website and it does not occur. Thanks for the quick response all the same and indeed for the plugin itself.