Hi @robmaric,
Thanks for following up! Your confusion is completely understandable, and you’re right to be skeptical.
To clarify what happened: the 4.9.2 release did attempt to fix this bug, but it introduced a regression of its own. The fix incorrectly hardcoded PST/PDT (America/Los_Angeles) as the timezone – based on the wrong ShipStation documentation. The correct reference is ShipStation’s Custom Store Development Guide, which specifies that start_date and end_date are sent in UTC – not PST/PDT and not the store’s local timezone.
This is why your Claude/Windsurf patch worked instantly: it applied a timezone conversion that the unmodified 4.9.2 code was missing entirely.
The correct fix is now merged and should ship in version 4.9.3. In the meantime, you can keep your local patch in place.
We appreciate you taking the time to document this so thoroughly!
I hope the following context will be helpful for developers of Sales Tax Reports For WooCommerce plugin:
While investigating a related issue, my colleague looked at the plugin code and identified two areas of potential issue. Basically, in both, every order is called (at once – with no paging or limit) and then the plugin attempts to loop through every order and build an array of data.
This happens on a site that has 17000 plus orders – too many to do this with. It’s a good idea to avoid calling “all” of anything without placing a limit on the call. To then try and loop through 17 000 orders in one go is too much for any website (the data alone probably is too much to hold in memory, but looping through to build another array of data as well).
Hi there,
Glad I could point you in the right direction! 🙂
This is indeed related to a bug in core WooCommerce:
https://github.com/woocommerce/woocommerce/issues/44677
The code has been fixed by our developers and the fix will be included in the next release of core WooCommerce plugin. Additional changes in Woo Subscriptions may or may not be necessary after that and our developers will determine that in the nearest future.
Hi @aimansogood,
Thank you for reaching out!
Before we continue, please note that Woo Subscriptions is a premium Woo.com extension and support is handled on Woo.com.
Our developers are aware of this issue and most likely this will be fixed in the next version of the core WooCommerce plugin. As a workaround, please check if WooCommerce > Settings > Advanced > Features > Order Attribution is enabled. If it is – please disable this feature and that should allow you to access subscriptions while our developers are working on a fix.
Hi @pvdm23,
I’m sorry to hear about the issues caused by Woo 8.5.0!
There was one particular bug due to which the release was retracted:
https://developer.woo.com/2024/01/09/woocommerce-8-5-0-released/#known-issue
https://github.com/woocommerce/woocommerce/issues/43406
This fatal error should not be the reason behind login/cart issues though so most likely there is some sort of a compatibility issue on your site. I’d recommend setting up a staging site (e.g. with WP Staging plugin), testing an update there, and perhaps performing a plugin/theme conflict test.
If you’ll need further assistance – please open a new thread. We will be marking this thread as resolved.
Hi @orangedam,
I’m glad if we could point you in the right direction with this!
I’ll be marking this thread as resolved but feel free to create a new one if you have other questions!
Hi @bbtr,
I completely understand why you’d prefer to wait for WooCommerce 8.5 to be re-released!
I’d rather wait for it to be officially re-released. As mentioned above 8.5 was released and then taken down, probably there is a reason it isn’t back yet. Better safe than sorry! 🙂 I just hope we won’t have to wait longer than Monday.
This particular vulnerability has been fixed in version 8.4 of WooCommerce a few weeks ago. That is confirmed by the text here:
https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/woocommerce/woocommerce-840-reflected-cross-site-scripting
IMPORTANT: There was a miscommunication and error in this vulnerability record where we initially reported version 8.5.0 as patched, while 8.4.0 was still vulnerable. This issue was patched in version 8.4.0 and only affects versions up to 8.3.0. Please rest assured knowing you can update the plugin to version 8.4.0 and this issue will be patched.
I can also confirm from the WooCommerce side that this issue has indeed been addressed in WooCommerce 8.4.0.
WooCommerce 8.5.0 has been released and then retracted due to an unrelated issue. It will likely be re-released early next week, however, there’s no rush to update since version 8.4.0 is secure.
I hope this helps!
Hi @orangedam
This vulnerability has been fixed in version 8.4 of WooCommerce which is confirmed by the text here:
https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/woocommerce/woocommerce-840-reflected-cross-site-scripting
IMPORTANT: There was a miscommunication and error in this vulnerability record where we initially reported version 8.5.0 as patched, while 8.4.0 was still vulnerable. This issue was patched in version 8.4.0 and only affects versions up to 8.3.0. Please rest assured knowing you can update the plugin to version 8.4.0 and this issue will be patched.
I can also confirm from our side that this issue has indeed been addressed in WooCommerce 8.4.0.
WooCommerce 8.5.0 has been released and then retracted due to an unrelated issue. It will likely be re-released early next week, however, there’s no rush to update since version 8.4.0 is secure.
I hope this helps!
Hi folks,
I wasn’t able to translate this text string via Loco Translate on my test site either so it looks like the translation is not working due to a different reason. After some further research, I see that the reason is described in a comment in this enhancement request:
https://github.com/Automattic/woocommerce-payments/issues/5007
Simply creating a translation in a “custom” location in Loco Translate is not enough and a second one needs to be added in the “System” location:
Screenshot direct link: https://d.pr/i/uwglMi
Screenshot direct link: https://d.pr/i/BaXpqv
Screenshot direct link: https://d.pr/i/MOxmMo
I’ve notified our developers about this inconsistency in translation workflow again.
It is also possible to change the text via a code snippet provided in this support document, and the Code Snippets plugin:
Screenshot direct link: https://d.pr/i/URFee5
Screenshot direct link: https://d.pr/i/KO0YRz
I hope this helps!
Hi there,
Thank you for the update, and no need to apologise!
I’m going to mark this thread as resolved.
Hi there,
Thank you for reaching out, and I’m glad to hear that you’re interested in using WooCommerce for your online business!
This site https://greekstateofmind.com/ is not built with WordPress/WooCommerce, however, it might be possible to find a theme that looks similar. At this time, I can’t recommend a specific theme I’m afraid but you’re more than welcome to check the ww.wp.xz.cn theme repository:
https://ww.wp.xz.cn/themes/#
If you decide to hire a designer – it might make sense to look into hiring someone from a platform such as Codeable, although it might be quite expensive compared to just finding a theme that already looks the way you need it to.
I hope this helps!
Hi there,
Thank you for reaching out!
I understand that you’re referring to this cart widget which works on your staging site but not on https://upsalacosmetic.com/ after an update:
Screenshot direct link: https://d.pr/i/u5lbxN
It does seem to work on the live site currently, were you able to fix it?
Screenshot direct link: https://d.pr/i/j0Xy48
In any case, please note that this isn’t added by the core WooCommerce plugin – it is likely added either by your theme or one of the additional plugins you’re using on this site. The support team of that plugin or theme should be able to help you address issues with the cart widget.
Since this question isn’t about the core WooCommerce plugin – I’ll be marking this thread as resolved.
Hi there,
Thank you for reaching out!
Technically, during the migration/overwrite of the live stage with the staging site, you’ll be performing a subscription migration which is a fairly complicated process and specifics depend on the payment methods you’re using, as well as the plugin you’re using for subscriptions.
You’ll need to export subscriptions from your current live site, import them to the new site, and then disable subscriptions on the old live site so that it doesn’t trigger duplicate subscription renewals.
If you’re using WooCommerce Subscriptions – please note that support of his premium extension is handled on WooCommerce.com, so please open a new ticket from the WooCommerce.com account you used to purchase the license.
More information can be found in these support documents:
https://woocommerce.com/document/migrating-subscribers-woocommerce-subscriptions/
https://woocommerce.com/document/subscriptions/subscriptions-handles-staging-sites/
https://woocommerce.com/document/subscriptions/add-or-modify-a-subscription/
Since this question isn’t about the core WooCommerce plugin – I’ll be marking it as solved.
I hope this helps!
Hi there,
Thank you for reaching out, and I’m sorry to hear about an order that is missing from the orders list in wp-admin!
As a first step, can you please confirm if this order was placed using the PayPal Payments extension? If yes – please open a new ticket on WooCommerce.com and select PayPal Payments from the dropdown – that way, the ticket will be forwarded to the support team of this extension. Please also include a link to this forum thread.
I have a feeling that this could be a result of some sort of a compatibility issue with the Polylang plugins you’re using on the site.
the headers and footers from “Elementor Header And Footer Builder” are not loading and there are none on the list in Dashboard (also the number on the counter is correct)
Another issue is that updating the theme to latest version, which has this “mini-cart” updated corrupts the design of the page, however this might be to the child theme / manual changes issue.
Since this is not something that can be reproduced with a default theme like Storefront, and here in this forum we don’t handle support of Elementor or your theme – we’ll have to ask you to reach out to support teams at Elementor and your theme.
I hope this helps!
Hi @laraaaustin,
Thank you for the follow-up, and I’m glad to hear that the origin of this behavior is now clear! Indeed, the support team of your theme should be able to provide some context/find a solution.
I’ll be marking this thread as resolved but feel free to start a new one if you’ll have other questions!
