Kowsar Hossain

Can anybody share the PHP error log via https://pastebin.com/ so that we can check? It should be available in cPanel or the hosting dashboard, or you can ask your hosting provider about it.

Also, which hosting service are you using? It would also be helpful if you could share the server information, which can be found in this screenshot: https://prnt.sc/D8D6wWFpRsA6

@lira123 Is it possible to share your website link so that I can take a look?

@dotch This is unusual, something that warrants checking the PHP error log. Are you by any chance using any CDN, e.g., Cloudflare? Is it possible to share the website link so that I can take a look? Have there been any recent changes made to the website, such as installing/updating a plugin, theme, or changing any plugin settings, etc.?

Hi @lira123, Could you please clarify what you mean by “purges itself right away when it's done preloading“? Are you saying that after clicking the Preload button and all pages are preloaded, for example, if the preload completes at 10:00, all pages are automatically purged at 10:01? Further clarification would help us understand better. Thanks.

Hi @wooplugins,

You’re right, The reason for this issue is that the plugin isn’t currently compatible with WooCommerce’s new HPOS feature, which was introduced in v8.2 and is enabled by default for newer WordPress installations. More details: https://woo.com/document/high-performance-order-storage/

It’s important to note that existing users will not be affected by this unless they manually enable the HPOS feature.

I have added HPOS compatibility to my to-do list and will try to work on it soon. Thank you very much for bringing this to my attention.

Hi @nguyenrom, I never thought of this feature before, since nobody asked for WPML support. I’ll keep this in mind.

And how many files are there in this case for a page? Would be helpful if you could share a screenshot

Update: We’ve concluded that we’ll be addressing this issue in a future release. Thank you once again for bringing it to our attention.

@opalcomp You’re right; it does seem unusual to find XML sitemaps in the cache directory. Thank you for pointing this out. I’ve made a note of it and will be discussing it with our team. If we determine that this is indeed a bug, we will work on resolving it. We’ll keep you updated on our findings. For now, you can exclude *.xml to avoid this.

If you manually click the Preload button, does it also trigger 6 requests per URL?

Thanks for providing the code reference. I’ve initiated an internal ticket in our system to conduct a more in-depth investigation. We’ll reach out to you if we require any additional information.

Hi,

It’s currently in the development phase. Please await the next release for the fix. Thanks

1. Do you have any multilingual plugins installed? If so, which one are you using?
2. Could you kindly provide a screenshot of the folder containing cached pages so that I can determine the number of files it contains? For instance, for the page at https://archseattle.org/about-the-archdiocese-of-seattle/archbishop-etienne/racial-justice/, the folder’s location might be wp-content/cache/wpo-cache/about-the-archdiocese-of-seattle/archbishop-etienne/racial-justice. As an illustrative example, in the screenshot linked here, you can observe that there are 5 files within that folder, screenshot: https://prnt.sc/DXfuBGt5I-mH

Yes, we’ll try to fix it in the next release. Until then, you can disable the Process JavaScript files option from the Minify tab to get things working. Thank you for reporting this.

You can attempt to exclude the URL of that website from the Advanced Cache Exclusion settings by navigating to Cache >> Advanced Settings >> URLs to exclude from caching . Here’s a screenshot for reference: https://prnt.sc/IFYhW1Fx2mNP