Title: Bug: Maintenance page cached
Last modified: November 25, 2019

---

# Bug: Maintenance page cached

 *  Resolved [Dave](https://wordpress.org/support/users/deeve007/)
 * (@deeve007)
 * [6 years, 6 months ago](https://wordpress.org/support/topic/bug-maintenance-page-cached/)
 * I put my site into maintenance mode for a short while over the weekend, to make
   some minor updates. Unbeknownst to me, after turning off maintenance mode, public
   users continued to see the maintenance page for 2 days until someone messaged
   me about it.
 * Yes, I’m aware I “should” have logged out of the site and checked it was working,
   and then deleted the cache to show the live site again. But surely your plugin
   should be able to recognize a maintenance page/setting and not cache that like
   it does with standard pages on the site?
 * For mine, this is a bug that should be fixed.

Viewing 11 replies - 1 through 11 (of 11 total)

 *  Plugin Author [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * (@emrevona)
 * [6 years, 6 months ago](https://wordpress.org/support/topic/bug-maintenance-page-cached/#post-12174432)
 * you are right so we created a hook for such issue. The plugin developer has to
   add the clear cache hook of the cache plugins. Here is our hook.
 * [https://www.wpfastestcache.com/tutorial/delete-the-cache-by-calling-the-function/](https://www.wpfastestcache.com/tutorial/delete-the-cache-by-calling-the-function/)
 *  Thread Starter [Dave](https://wordpress.org/support/users/deeve007/)
 * (@deeve007)
 * [6 years, 6 months ago](https://wordpress.org/support/topic/bug-maintenance-page-cached/#post-12174463)
 * So every plugin developer has to add your custom function into their plugin?
   (
   along with every other caching plugin custom function I’d imagine they’d need
   to do)
 * Wouldn’t it be easier to exclude any page from your caching that doesn’t include
   wp_head() in the header or similar, as these maintenance pages tend not to?
 * Also, doesn’t this function clear the entire cache? But why would you want that
   as the default option, surely it’s just about NOT caching the maintenance page,
   but leaving other cached pages as they are?
    -  This reply was modified 6 years, 6 months ago by [Dave](https://wordpress.org/support/users/deeve007/).
 *  Plugin Author [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * (@emrevona)
 * [6 years, 6 months ago](https://wordpress.org/support/topic/bug-maintenance-page-cached/#post-12174825)
 * ok I can add a hook for you 🙂 can you tell me the plugin name please?
 *  Thread Starter [Dave](https://wordpress.org/support/users/deeve007/)
 * (@deeve007)
 * [6 years, 6 months ago](https://wordpress.org/support/topic/bug-maintenance-page-cached/#post-12174832)
 * [https://wordpress.org/plugins/lj-maintenance-mode/](https://wordpress.org/plugins/lj-maintenance-mode/)
 * I appreciate it, but wouldn’t it make more sense to add code that would work 
   with any maintenance mode plugin? Surely it couldn’t be that hard to determine
   if that type of page is being displayed?
    -  This reply was modified 6 years, 6 months ago by [Dave](https://wordpress.org/support/users/deeve007/).
 *  Plugin Author [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * (@emrevona)
 * [6 years, 6 months ago](https://wordpress.org/support/topic/bug-maintenance-page-cached/#post-12174873)
 * ow sorry, this is not a big plugin and it has not been updated for 2 years.
 *  Thread Starter [Dave](https://wordpress.org/support/users/deeve007/)
 * (@deeve007)
 * [6 years, 6 months ago](https://wordpress.org/support/topic/bug-maintenance-page-cached/#post-12174888)
 * I truly don’t understand why you are wanting to create some sort of exception
   for any individual plugin, this one or otherwise??
 * This “should” be default functionality in any plugin, that it only works for 
   the pages/screens it is required to work on, and a maintenance page very obviously
   does not require caching by default. This should be a bug to be fixed, not a 
   special request for functionality.
 * Obviously it’s a free plugin so there’s only so much I can say about this, but
   I simply am at a loss as to why you wouldn’t regard this as a bug to be fixed
   for all maintenance style plugins?
    -  This reply was modified 6 years, 6 months ago by [Dave](https://wordpress.org/support/users/deeve007/).
 *  Plugin Author [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * (@emrevona)
 * [6 years, 6 months ago](https://wordpress.org/support/topic/bug-maintenance-page-cached/#post-12178798)
 * I can add a hook for you but even the developer does not answer the questions.
 * [https://wordpress.org/support/plugin/lj-maintenance-mode/](https://wordpress.org/support/plugin/lj-maintenance-mode/)
 *  Thread Starter [Dave](https://wordpress.org/support/users/deeve007/)
 * (@deeve007)
 * [6 years, 6 months ago](https://wordpress.org/support/topic/bug-maintenance-page-cached/#post-12178816)
 * Again, why wouldn’t you fix the issue so it works with ALL maintenance type plugins??
   This shouldn’t be a “per plugin” fix surely, I really don’t understand why you
   wouldn’t want to fix this bug for ALL maintenance plugins, current and in the
   future?
 * I mean, it’s really simple:
    – For any front-end page that doesn’t use the current
   active theme, don’t cache it. – Add an unchecked checkbox option in your settings
   if a user wants to cache those pages too (there may be some strange reason someone
   wants to).
 * That should be a pretty simple thing to do. I’ve been quoted 2 to 3 hours work
   max from a number of developers on Upwork, where you can hardly ever find great
   developers so I’m sure it can be done faster by a good developer.
    -  This reply was modified 6 years, 6 months ago by [Dave](https://wordpress.org/support/users/deeve007/).
 *  Plugin Author [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * (@emrevona)
 * [6 years, 6 months ago](https://wordpress.org/support/topic/bug-maintenance-page-cached/#post-12178821)
 * There cannot be a common solution for this but if you have an idea about I want
   to listen to you.
 *  Thread Starter [Dave](https://wordpress.org/support/users/deeve007/)
 * (@deeve007)
 * [6 years, 6 months ago](https://wordpress.org/support/topic/bug-maintenance-page-cached/#post-12178835)
 * I just outlined the very obvious solution:
    1) If any page is not using the current
   active theme (this is easy to detect), don’t cache it automatically. 2) Add a
   checkbox in settings so someone can optionally include these pages in the cache
   too.
 * This isn’t a hard thing to do surely?? And then you’ve addressed the issue for
   ALL maintenance plugins. I mean, if I ever decide to switch to another one (no
   reason to at present, that one works perfectly) the same bug will simply happen
   again each time.
    -  This reply was modified 6 years, 6 months ago by [Dave](https://wordpress.org/support/users/deeve007/).
 *  Plugin Author [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * (@emrevona)
 * [6 years, 6 months ago](https://wordpress.org/support/topic/bug-maintenance-page-cached/#post-12185534)
 * I will think about it. thank you.

Viewing 11 replies - 1 through 11 (of 11 total)

The topic ‘Bug: Maintenance page cached’ is closed to new replies.

 * ![](https://ps.w.org/wp-fastest-cache/assets/icon-256x256.png?rev=2064586)
 * [WP Fastest Cache - WordPress Cache Plugin](https://wordpress.org/plugins/wp-fastest-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-fastest-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-fastest-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-fastest-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-fastest-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-fastest-cache/reviews/)

 * 11 replies
 * 2 participants
 * Last reply from: [Emre Vona](https://wordpress.org/support/users/emrevona/)
 * Last activity: [6 years, 6 months ago](https://wordpress.org/support/topic/bug-maintenance-page-cached/#post-12185534)
 * Status: resolved