Title: Fallback problem Last modified: March 9, 2023 --- # Fallback problem * Resolved [Carlo Buttinoni](https://wordpress.org/support/users/buttinoni/) * (@buttinoni) * [3 years, 1 month ago](https://wordpress.org/support/topic/fallback-problem/) * hello everyone, * I have a problem with my site [Carlo Buttinoni fotografo](https://www.buttinoni.it/): if I activate the fallback page cache, all the published pages have problems ( some keys, arrows, the drop-down menu, etc. are no longer visible) how can I fix? * the published page now don’t have the fallback.. * the test page: Page caching is working for static page but seems not working for dynamic pages. Error on dynamic page ([https://www.buttinoni.it](https://www.buttinoni.it)): Cache status: DYNAMIC – The resource was not cached by default and your current Cloudflare caching configuration doesn’t instruct Cloudflare to cache the resource. Instead, the resource was requested from the origin web server. Error on static resource (/wp-content/plugins/wp-cloudflare-page-cache/assets/testcache.html): Cache status: DYNAMIC – The resource was not cached by default and your current Cloudflare caching configuration doesn’t instruct Cloudflare to cache the resource. Instead, the resource was requested from the origin web server. * tanks - This topic was modified 3 years, 1 month ago by [Carlo Buttinoni](https://wordpress.org/support/users/buttinoni/). - This topic was modified 3 years, 1 month ago by [Carlo Buttinoni](https://wordpress.org/support/users/buttinoni/). - This topic was modified 3 years, 1 month ago by [Carlo Buttinoni](https://wordpress.org/support/users/buttinoni/). * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ffallback-problem%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 5 replies - 1 through 5 (of 5 total) * Plugin Contributor [iSaumya](https://wordpress.org/support/users/isaumya/) * (@isaumya) * [3 years, 1 month ago](https://wordpress.org/support/topic/fallback-problem/#post-16546152) * Hi [@buttinoni](https://wordpress.org/support/users/buttinoni/), I don’t think fallback cache is causing the problem here, in fact it seems something else might be causing the problem which is becoming evident when you are enabling the fallback cache. The fallback cache does not have any power to do it. It simply just cache the page HTML in the disk. That’s it. * Looking at the response header of your website it seems that the plugin is not handling the `cache-control` header of your webpage, instead you either have some other server level page caching system or some plugin that is overwriting the header value. * When the plugin is active, the value of `cache-control` and `x-wp-cf-super-cache- cache-control` should match. Which is not the case for your website: [https://i.imgur.com/OgshkCj.jpeg](https://i.imgur.com/OgshkCj.jpeg) * Also looking at your response header it seems you have some other caching system active along with this plugin. Screenshot: [https://i.imgur.com/HeeySzS.jpeg](https://i.imgur.com/HeeySzS.jpeg) * It is highly recommended not to use more than one page caching solution when using this plugin as it might cause conflict between these systems. I think this is what causing the problem. If you remove this other host level caching system and only use this plugin, then I don’t think you will face these problems. * Thread Starter [Carlo Buttinoni](https://wordpress.org/support/users/buttinoni/) * (@buttinoni) * [3 years, 1 month ago](https://wordpress.org/support/topic/fallback-problem/#post-16549618) * I have try do disable the siteground cache (nemcache) and all preference in the siteground panel (in the site siteground) but the response is the same…. * i don’t have any plugin installed * you can try? * Thread Starter [Carlo Buttinoni](https://wordpress.org/support/users/buttinoni/) * (@buttinoni) * [3 years, 1 month ago](https://wordpress.org/support/topic/fallback-problem/#post-16549627) * if i use the your button? “Overwrite the cache-control header for WordPress’s pages using web server rules” * Thread Starter [Carlo Buttinoni](https://wordpress.org/support/users/buttinoni/) * (@buttinoni) * [3 years, 1 month ago](https://wordpress.org/support/topic/fallback-problem/#post-16549721) * the only plugin activated is LITESPEED CACHE SETTINGS (the cache is always deactivated) it is recognized by your plugin, but I think this is what causes problems: * in fact, if I activate fallback and insert in : Prevent the following URIs to be cached the string: https:/ /www.buttinoni.it/wp-content/plugins/litespeed- cache/guest.vary.php * everything works but I lose in optimization of litespeed…. * help…. * Plugin Contributor [iSaumya](https://wordpress.org/support/users/isaumya/) * (@isaumya) * [3 years, 1 month ago](https://wordpress.org/support/topic/fallback-problem/#post-16554077) * Hi [@buttinoni](https://wordpress.org/support/users/buttinoni/), Sorry for the delayed reply due to the weekend. I just checked the response header of your website and everything is same as I looked at it. If you have reverted the changes, can you please re-implement the changes so that I can take a look at it? Thanks. Viewing 5 replies - 1 through 5 (of 5 total) The topic ‘Fallback problem’ is closed to new replies. * ![](https://ps.w.org/wp-cloudflare-page-cache/assets/icon-256x256.gif?rev=3234997) * [Super Page Cache](https://wordpress.org/plugins/wp-cloudflare-page-cache/) * [Frequently Asked Questions](https://wordpress.org/plugins/wp-cloudflare-page-cache/#faq) * [Support Threads](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/) * [Active Topics](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wp-cloudflare-page-cache/reviews/) * 5 replies * 2 participants * Last reply from: [iSaumya](https://wordpress.org/support/users/isaumya/) * Last activity: [3 years, 1 month ago](https://wordpress.org/support/topic/fallback-problem/#post-16554077) * Status: resolved