Hi @maltfield,
Thanks for the detailed report, and great catch reporting this directly on GitHub yourself, that’s really helpful for the dev team!
Totally understandable that you couldn’t test directly with Tor given the IP blocking on your end; no need to chase that further. Since you’ve already filed #66102 and the team has confirmed it as a bug and assigned it, they have what they need to take it from here.
One thing that would help speed things along: could you add your site’s System Status Report to the GitHub issue, under the “WordPress Environment” section (currently marked “n/a”)? You can find it via WooCommerce → Status. Click Get system report, then Copy for support (after scrolling down a bit), and paste it directly into the issue, or link to a Pastebin/gist if you’d rather not paste it inline. That’ll give the dev team your exact environment details to help reproduce and verify the fix.
Thanks again for the clear write-up.
> Totally understandable that you couldn’t test directly with Tor given the IP blocking on your end
Just to clarify: I don’t block Tor.
A large number of my customers use Tor Browser, and I first confirmed this bug with Tor Browser.
Because Tor Browser is the most popular security-hardened browser available, and because so many security-conscious customers use it for purchasing goods on e-commerce sites powered by woocommerce, I highly suggest that woocommerce devs test your releases directly with Tor Browser (configured to “Safest” mode)
> Since you’ve already filed #66102 and the team has confirmed it as a bug and assigned it, they have what they need to take it from here.
The woocommerce team hasn’t yet confirmed it. A bot assigned it automatically. There’s no indication that the woocommerce devs have seen it yet.
A third party offered to write a PR for it, but the woocommerce devs haven’t yet responded.
I would appreciate it if you could raise this to the attention of one of your devs. And maybe let them know that this bug was discovered by a human — not reported by an AI bot.
Hi @maltfield!
Thank you for providing more information about the issue. I can understand your concern.
I checked the bug report you submitted, and I can confirm that it has already been assigned to one of our team members, who is currently investigating the issue. You should also be able to see that the GitHub issue has been assigned.
For now, I’d recommend waiting while our team completes their investigation. They’ll provide updates directly on the GitHub thread as they become available.
Thank you for your cooperation and understanding.
