Also in the same situation and was wondering as well.
Thanks
Yes wondering the same – have checked the Blog, Github repo and nothing there – I don’t see any major issue on the Support forum.
All of our client sites are running either 7.2 or 7.2.1 and we would like someone from the Woo team to advise what is the heck is going on with this.
Me too – I made yesterday few updates and now I see that 7.2.1 disappeared.
Same here, would love to have some feedback what is going on.
I did have issues on one of the sites with Woo DB update actions not updating DB and constantly getting scheduled over and over again.
I did have issues on one of the sites with Woo DB update actions not updating DB and constantly getting scheduled over and over again.
Same story. I updated WC to 7.2.1 and now my log is full of warnings related unsuccessful WC database migration.
I would expect at least some sort of quick announcement from devs about what happened and why current latest version is 7.1.1.
Leaving millions of store owners and developers guessing what happened is rather disrespectful.
Back to 7.2.1 again now. I hope they have fixed the hardcoded table prefix bug…
Note to all:
Wait with upgrading until 7.2.2. This to avoid the above mentioned bug!
Apologies for this — as @nipter pointed out, there was a pretty serious bug that caused us to “pull back” 7.2.1, but then there was a mess up with the stable tag definition in SVN. We’re fixing it now (you will see the stable version go back to 7.2.0 for now), and would suggest waiting for 7.2.2 before any further updates.
If you’re already running 7.2.1 then you should be fine — the issue was this one, so if you don’t change your table prefixes, or perhaps didn’t need that migration, then everything else should be normal. You would have seen this as a major problem during update if it was going to be one.
Radio silence from the Woo team is very unsettling! Not only that, received an eNewsletter from WooCommerce this morning talking about version 7.2
With WooCommerce 7.2, we’ve introduced measures to protect stores from API attacks with the option of a rate limiting function. Once enabled, you’ll be able to automatically block, track, and handle instances of a single user ID or IP address trying to overwhelm the store by sending multiple requests in a short time.
You’ll also want to make sure it works with proxies and load balancers, so check out Paulo’s guide to get the filters and actions you need.
WooCommerce
Really wish we knew what was happening. I checked our logs and didn’t notice anything out of the ordinary so we haven’t rolled anything back yet.
Thank you for the update @beaulebens.
@viablethought I’m one of the Woo team, so not radio silence — the rest of the team is getting things fixed and making sure they know what happened before any further communication. Please see my comment above.
The quote from the newsletter is completely unrelated to this BTW. That’s an enhancement our team working on some of our APIs added as they were reviewing possible ways of attacking/overloading stores (we haven’t seen it in the wild, it was added preventatively).
@beaulebens – Thanks a lot for the update!
@beaulebens – understood, your response was added within a minute of my last one, but up until your response, it had been almost 18 hours with 0 information about what was happening. Hence my last post.
The newsletter spoke of version 7.2 in a time where we had no new information about what was going on, it was just confusing.
All good though.
