To solve the issue. You need to clear the browser history and cache for your website with version 3.0.2. This will fix the schedule period bug.
Hello,
the new version causes errors displayed in the admin panel as well as on the website. Does the new version have special requirements other than the previous one?
I had to turn it off 🙁
I can’t tell the owners of my shops to clear their browsers just to make your plugin work again. This is not supposed to work like this.
So I just tried wiping all my cache on a test shop on a local LAMP server, and the bug described in the first post is still there. On a distant server (on an active shop I run) I can confirm what @ppaatt is saying is there too, errors throwing in every admin panel pages.
We’re trying to reproduce the behavior being described here, but haven’t been able to reproduce.
Can you send us the actual errors. This will allow us to troubleshoot quicker. Without the error logs or screenshots it will take us longer to investigate. Thanks!
We are pushing a new version, 3.0.3 to hopefully fix the issues reported, since we are unable to fully reproduce the errors, please let us know if this fixes the issue.
If no, please update the post here with the log information of the errors you are encountering. Logs will allow us to continue troubleshooting the issue.
Hello,
in a few hours I will be able to plug in and check for errors. The restaurant is now accepting orders so I can’t turn it on. Give me a moment and I’ll send screenshots with errors
Thanks for the update. Make sure the latest version 3.0.3 is active.
Please grab the screenshots and logs you encounter. If you could also send us any error logs from WooCommerce under System, Logs. And look for any errors related to zhours. One final thing the WooCommerce system report for the site would be helpful for us to review as well. You can find it at WooCommerce, System. Get System Log. So we can try and reproduce the environment.
We look forward to your update.
hi,
it’s the same problem on version 3.0.3.
I have woocommerce version 3.8.1 – can this be the reason?
link to preview: https://ifotos.pl/z/qanaeqw
We have been trying to reproduce these logs with no luck. Even running 3.8.1
Can you bump to the latest WooCommerce 3.9.1, verify if the logs are still triggering?
And let’s have you perform the theme/plugin conflict testing to see if the logs are linked to another active plugin. If you bump to 3.9.1 and running only WooCommerce and Order Hours with Storefront theme, this should give us a clean environment to see if the errors are still triggering. If the errors are fixed, add a new plugin one by one to isolate the issue.
Go ahead and upgrade to the latest version 3.0.5.
Using the screenshots you provided showing the error logs, I think this latest release will resolve the errors officially now.
Closing this support issue as resolved. If the issue is still occurring, please re-open the support forum post here with more details and screenshots of errors generated.