adeelkhan

First of all, sorry for the inconvenience you have faced.

Could you please confirm whether the permission error has been resolved after resetting permissions from the server end, as mentioned in the reference link?

Thank you for your feedback and kind words.

Thank you for your feedback and kind words. Your support means a lot to us.

To better understand the issue you’re facing, could you please share the specific line of code mentioned in the file /home/teq/webapps/teqfit/wp-content/plugins/onestock-for-woocommerce/src/Cache/NetworkProductCache.php

Your cooperation in providing this information will greatly assist in pinpointing the root cause and facilitating a more accurate resolution to the matter.

Please share the logs.

The error suggests a configuration issue, pointing to a potential problem with cache configuration. Specifically, there seems to be an issue at the following path: /home/teq/webapps/teqfit/wp-content/plugins/onestock-for-woocommerce/src/Cache/NetworkProductCache.php on line 40.

?it would be great if you contact our support and?create ticket?. We will investigate the point of conflict and also share to our users.

Thank you for providing the details, and I’m pleased to hear that you’ve identified a workaround for the broken site access.

Regarding Gzip, are there any warnings or errors appearing in the console log or debug log?

When updating a single post, Breeze purges the cache only for relevant post/page, not for the entire site. Clicking ‘Purge All Cache’ will clear the cache for the entire site.

This issue is unrelated to the Breeze plugin. Please reconfigure the key of the OneStock plugin as indicated in the error message.

Additionally, have you installed a different cache plugin along with Breeze?

• This reply was modified 1 year, 3 months ago by adeelkhan.

Kindly review the error log to pinpoint the source of the conflict.

Please share the error.

The point has been implemented.

Please update 2.1.1

Please update 2.0.33

Thanks for sharing your approach.

Breeze cache entire page while user visit the application and create cache of it. Once any content update so Breeze execute its purge request to show the update version and cache it again. The approach you have discussed not compatible with Breeze.

Please update 2.0.33. The point has been fixed.