Marko Vasiljevic

Hello Hunter,

Thank you for reaching out, and I am happy to help!
When the W3 Total Cache Pro was purchased and when you subscribed to the W3 Total Cache Pro version, you accepted the terms and conditions, specifically section 12.2 Automatic Renewal of Premium Subscription Plans https://www.boldgrid.com/w3-total-cache-policies/.

This was the 8th annual renewal for the W3 Total Cache Pro plugin! As for the previous renewals, the ” Renewal Reminder ” email was sent to the email address used to subscribe to W3 Total Cache Pro, hunter@ one week prior to the renewal of the license on Jun 12, 2025 12:26 AM EDT.
Let me know if this helps!

Hello Kevin!

Thank you for reaching out, and I am happy to help!
Have you tried configuring the Page Fragment Cache in the W3 Total Cache as in the wiki page shown here, and let me know if the implementation is successful!?
Thanks!

Hello Amal,

Thank you for reaching out and I am happy to help!
When you purchased the W3 Total Cache Pro and a subscription was created, you accepted the terms and conditions:

By ordering, you are agreeing to our complete Terms of Use. You authorize us to charge your card now and at the time of your renewal annually. You can cancel this subscription at any time by e-mailing customer-support@w3-edge.com.

The Renewal reminder email is sent to the email address used for subscription (In your case, the email you submitted for this topic) seven days prior to the renewal. The email will arrive on June 25th or 26th, depending on the timezone
Do you need to update the billing for the next update?

Thanks!

Hello Graziano,

Thank you for reaching out and I am happy to help!
Thank you for the detailed report and for providing the environment information.

Based on what you’ve shared, we would not currently expect W3 Total Cache itself to trigger this type of memory exhaustion error through page cache priming or normal page cache generation.

Regarding your first question, page cache priming works by making standard HTTP requests to the URLs being primed. Those requests go through the normal WordPress bootstrap process, which includes loading the active theme and calling functions such as get_template() and get_stylesheet(). As a result, a priming request could encounter the error if another plugin or theme callback attached to the template or stylesheet filters is causing a problem. However, the priming process itself does not modify or hook those filters.

For your second question, the primary W3 Total Cache code paths that hook the template and stylesheet filters are related to theme switching for Mobile Groups and Referrer Groups. Since both mobile.enabled and referrer.enabled are disabled in your configuration, those callbacks should not be active. We are not aware of other core page cache, minify, CDN, or output buffering features that attach to these filters under normal operation.

Regarding PHP 8.4 compatibility, we are not aware of any known issues in current W3 Total Cache releases that would cause recursive theme detection or excessive memory allocation through the template filter. The allocation size shown in the error log (approximately 4 GB) is unusual and is more consistent with a recursive callback chain or another component repeatedly invoking theme-related functions.

As a diagnostic step, we would recommend inspecting the callbacks currently attached to the template and stylesheet filters when the issue occurs. If another plugin or theme is calling get_template(), get_stylesheet(), or wp_get_theme() from within one of those filter callbacks, it could create the type of recursive behavior suggested by the error.

If you’re able to provide a W3 Total Cache configuration export, a stack trace, or a list of callbacks attached to the template filter, we’d be happy to review them and help determine whether W3 Total Cache is involved.

Hello,

Thank you for reaching out, and I am happy to help!
We’ve received yoru email via the W3 Total Cache support channel and provided the information there.
Thanks!

Hello Jan,

Thank you for reaching out, and I am happy to help!
I’ve reset the active URL.

Remove the license key from the W3 Total Cache – Performance>General settings, Licensing sub-box, license field, and save all settings. Re-enter the license and save all settings.

W3 Total Cache Pro should be active after these steps!

Thanks!

Hello Peter,

Thank you for reaching out and I am happy to help!

This happens because many WooCommerce REST API updates and some third-party plugins bypass the normal WordPress post update flow that W3 Total Cache listens to for automatic cache purging.
Updates made through WooCommerce CRUD objects, REST API endpoints, or bulk stock management plugins can bypass cache invalidation completely.

Just to confirm, if you manually purge the cache or a specific product the stock updates?
Thanks!

Hello Hailin,

Thank you for reaching out, and I am happy to help!
We’ve received your email via the W3 Total Cache support channel and replied to it with the instructions! Please check yoru email and follow the instructions there
Thanks!

Hello Jake,

Thank you for reaching out, and I am happy to help!
There is a lot of documentation available for the W3 Total Cache, and you can find more developer-oriented documentation in our GitHub wiki page:
https://github.com/BoldGrid/w3-total-cache/wiki

I hope this helps!

Thanks!

Hello Konstantinos,

Thank you for reaching out and thank you for yoru patience!
We’ve fixed this in the latest W3 Total Cache release, so please make sure to update to the latest version, and the token length issue should be resolved

Thanks!

Hello Johnny,

Thank you for reaching out and I am happy to help!
What you are seeing is a placeholder for the lazy-loaded images, which is added when the Lazy Loading option is enabled in the W3 Total Cache.
This being said, potentially, you are using some other lazy-loading option in the theme or some other plugin, which may be creating the conflict.
Can you please disable Lazy Loading in Performance>General Settings>User Experience section and let me know if the issue persists?
Thanks!

Hello Eugene,

Thank you for reaching out and I am happy to help!
Can you please reach out to us directly via the W3 Total Cache support channel at customer-support@w3-edge.com so we can avoid sharing any sensitive information in the public forum?
Please share your subscription details in the email
Thanks!

Hello James,

Thank you for reaching out, and I am happy to help!
As you know, we have received your email via the W3 Total Cache support channel and provided support there.
Thank you!

Hello,

You are most welcome!

We would really appreciate it if you could take a minute and post a review here. This will help us to continue offering a top-notch product to users.
Thanks!

Hello Andreas

Thank you for reaching out, and I am happy to help!
Can you please reach out directly to the W3 Total Cache support channel via the email customer-support@w3-edge.com and specify this forum topic so we can assist you with this?
Please include the information in the email body

Thanks!

Hello Zitzmann,

I am sorry about the issue you are experiencing and I am happy to help!
We are aware of the issue you are experiencing, and we are working on a fix for this. Currently, version 2.9.3 has been released, which does not resolve the issue at the moment.

Please keep the working version W3 Total Cache 2.9.2 until the fix is released.

https://downloads.wordpress.org/plugin/w3-total-cache.2.9.2.zip

We are working on the patch for this, and it will be relased asap!

Thanks!

Hello,

I am sorry about the issue you are experiencing and I am happy to help!
We are aware of the issue you are experiencing, and we are working on a fix for this. Currently, version 2.9.3 has been released, which does not resolve the issue at the moment.

Please keep the working version W3 Total Cache 2.9.2 until the fix is released.

https://downloads.wordpress.org/plugin/w3-total-cache.2.9.2.zip

We are working on the patch for this, and it will be relased asap!

Thanks!

Hello Ivo,

I am sorry about the issue you are experiencing and I am happy to help!
We are aware of the issue you are experiencing, and we are working on a fix for this. Currently, version 2.9.3 has been released, which does not resolve the issue at the moment.

Please keep the working version W3 Total Cache 2.9.2 until the fix is released.

https://downloads.wordpress.org/plugin/w3-total-cache.2.9.2.zip

We are working on the patch for this, and it will be relased asap!

Thanks!

Hello Mark

Thank you for your question and we are sorry about the issue you experienced!
We appreciate your feedback, and we are fixing the issue that will resolve the problem.
Please keep the W3TC version on 2.9.2 and wait for the upcoming patch release

Thank you for your patience!

Hello Jaime,

Thank you for reaching out and I am happy to help!
We’ve received your email via the W3 Total Cache support channel. Please check your email and continue any correspondence there so we can avoid duplicating the answers.
Thanks!