William Staley

Hi @peterjaegerto. We have documented some known issues with the release of 8.6.0 and added some workarounds for those issues. We are working now on getting a new release in place. We will post more details about that release to our blog when they are available.

@erwin99 There are some known issues with the release of 8.6.0. We have published them here and are working on a fix release. We have listed the available workarounds for those who are experiencing problems. Please take a look and let me know if this has fixed your problem.

I wanted to pop in to provide a follow up to our release of 8.5. There were some issues with the release that were likely the culprit of some of what was seen in this thread. After finding the problem we reverted the stable tag to 8.4 and are working to fix the issue. We expect to have a fix in place by Monday, January 15th and release 8.5.1. More info can be found in the release notes for 8.5 and we will be publishing an advisory to our blog soon.

@caban13 Yes, we are aiming to release 8.5.1 on Monday, January 15th. Please keep an eye on the developer blog for the most up to date information.

@senjoralfonso Thank you for bringing this up. We had identified this issue shortly after releasing 8.5. We subsequently reverted the stable tag back to 8.4 and added an update to our release notes acknowledging the problem and providing a workaround. Apologies for the problems here. We should be releasing 8.5.1 on Monday, January 15th, but keep an eye on our developer blog for the most up to date information.

@scruffy1 & @alizesonline, the issue was uncovered around the same time as the release notes for 8.5 going out, so we added a note to that post about the known issue. We are working to get 8.5.1 out soon, but we are testing internally to ensure its readiness so will likely be releasing it on Monday, January 15th.

Hi @skym199. Could you provide us with any further details so we might be able to assist here? Is the site available and you simply can’t enable HPOS? What do you mean by “showing inactivity?” Do you still have access to your system status report via the admin? If so, could you provide it here so that we might be able to dig into this further?

@graphicadhumboldt thank you for following up. Going to mark this resolved for now.

Hi @graphicadhumboldt. Just a heads up that we recently released a new fix release (7.7.2). I’m hoping this addresses the issue you are experiencing.

Hi @megadive,

Very sorry about the trouble here. I believe the problem you are experiencing has an open issue that is currently being addressed and will be fixed soon. You can track the progress in GitHub.

If this does not look correct, could you provide more information on the details of the 500?

Hi @prwordpressorg,

Very sorry about the trouble here. There is an open issue for this that is currently being addressed and will be fixed soon. You can track the progress in GitHub.

Hi @midipedalboards. I am sorry for the annoying messages. It is quite possible this is a bug, mixed with an enhancement where we could possibly remove messages that do not apply (such as shipping messages for those who have shipping disabled). Typically our bug reports go through GitHub. If you have a GH account you are always welcome to open an issue over here.

Sharing this with you now so you are aware of its existence, but it is true we could make our bug reporting more accessible.

Hi @itsmefti, I wanted to let you know that this is a known issue and there is a GH issue attached and being worked on.

https://github.com/woocommerce/woocommerce/issues/36855

Hi @mr2od, I just wanted to let you know that this is a known issue and has been discussed here. There is an open GH issue where you can track the status.

Hi @boxingkoala. Interesting bug find. If you have any sense of how this might be resolved in code or have any other details I’d recommend creating an Issue in GitHub here: https://github.com/woocommerce/woocommerce/issues