Title: Planned Outage for Block Themes Author: Troy Chaplin Published: 2026-يىلى 29-يانۋار Last modified: 2026-يىلى 14-ئىيۇل --- قىستۇرما ئىزدە ![](https://ps.w.org/planned-outage/assets/banner-772x250.png?rev=3449795) ![](https://ps.w.org/planned-outage/assets/icon-256x256.png?rev=3449795) # Planned Outage for Block Themes يازغۇچى [Troy Chaplin](https://profiles.wordpress.org/areziaal/) [چۈشۈر](https://downloads.wordpress.org/plugin/planned-outage.1.4.0.zip) * [تەپسىلاتلار](https://ug.wordpress.org/plugins/planned-outage/#description) * [باھالاشلار](https://ug.wordpress.org/plugins/planned-outage/#reviews) * [ئورنىتىش](https://ug.wordpress.org/plugins/planned-outage/#installation) * [ئىجادىيەت](https://ug.wordpress.org/plugins/planned-outage/#developers) [قوللاش](https://wordpress.org/support/plugin/planned-outage/) ## چۈشەندۈرۈش Planned Outage for Block Themes is a lightweight plugin that enables maintenance mode for WordPress block themes. When enabled, logged-out visitors see your custom maintenance template while logged-in users can browse the site normally. **Features:** * Uses native block theme templates * Create maintenance pages in the Site Editor or as theme files * Schedule outage windows with a start and end time — maintenance turns on and off automatically * Logged-in users bypass maintenance mode * Configurable expected duration (Retry-After header); during a scheduled window the header reflects the time remaining automatically * Pre-launch mode for sites that aren’t live yet * Optional search engine bot access during maintenance * Bypass link to let non-logged-in users preview the site during maintenance * Admin bar indicator when maintenance mode is active * Duration warning after 3 days of maintenance (except in pre-launch mode) * Returns proper 503 status code for SEO * Cache plugin detection with admin warning and automatic cache flushing **Requirements:** * WordPress 6.6 or higher * A block theme (like Twenty Twenty-Five) ## ئورنىتىش 1. Upload the plugin folder to your /wp-content/plugins/ folder. 2. Go to the **Plugins** page and activate the plugin. 3. Create a maintenance template (see FAQ below). 4. Go to **Settings > Planned Outage** and enable it. ## FAQ ### How do I create a maintenance template? You have two options: 1. **Site Editor:** Go to Appearance > Editor > Templates, create a new template named« maintenance» 2. **Theme file:** Add a `maintenance.html` file to your theme’s `/templates/` folder ### How does scheduling work? Set a start and end date/time under Settings > Planned Outage (times are entered in your site’s timezone). Maintenance mode activates automatically when the window begins and deactivates when it ends — no manual toggling and no reliance on WP-Cron: the window is checked on every request, so the switch is exact. The manual toggle still works independently; maintenance is active if either the toggle is on or the current time is inside the window. During a scheduled window the Retry-After header automatically reflects the time remaining. ### Does the maintenance template show during WordPress core, plugin, or theme updates? No, and this is a WordPress limitation rather than a plugin bug. During a real update WordPress creates a `.maintenance` file and ends the request very early in its boot process — before any plugin code loads — showing its built-in «Briefly unavailable for scheduled maintenance» screen. No plugin can render a block template at that point. These windows are short (WordPress considers maintenance over after 10 minutes) and only occur during actual updates. If you want a custom page for those moments, WordPress supports a hand-made `wp-content/maintenance.php` drop-in, which is independent of this plugin. ### Who can see the site when maintenance mode is enabled? All logged-in users can browse the site normally. Only logged-out visitors see the maintenance template. You can also enable search engine bots to bypass maintenance mode, or generate a bypass link for non-logged-in users. ### What is the Expected Duration setting? This sets the Retry-After HTTP header, which tells search engines how long to wait before checking your site again. Options range from 30 minutes to 1 day. You can also select «Pre-Launch (indefinite)» for sites that aren’t live yet, which disables duration tracking and admin warnings. ### What is the Bypass Link? When enabled, the plugin generates a secret URL you can share with anyone who needs to view the site during maintenance without logging in. A 12-hour cookie is set on first visit so they can navigate freely. You can regenerate the link at any time to invalidate the previous one. ### Should I enable Search Engine Access? For short maintenance periods (under 2 hours), the default settings are fine. For longer maintenance (over 2 hours), consider enabling search engine access. For maintenance lasting more than a day, always enable it to prevent pages from being removed from search indexes. ### What status code is returned? The plugin returns a 503 (Service Unavailable) status with a Retry-After header, which tells search engines the site is temporarily unavailable. ### Will this work with caching plugins? The plugin detects popular full-page cache plugins (Surge, WP Super Cache, W3 Total Cache, WP Fastest Cache, LiteSpeed Cache, WP Rocket) and displays a warning on the settings page when one is active. Caches are automatically flushed when settings are saved to ensure the maintenance page is served immediately. Server-level caches (Nginx FastCGI cache, Varnish, Cloudflare, etc.) cannot be detected or flushed by the plugin. If maintenance mode is not working and you use server- level caching, flush that cache manually. ### How to uninstall the plugin? Simply deactivate and delete the plugin. The plugin stores options prefixed with` pobt_` which are removed when you deactivate the plugin. ## باھالاشلار ![](https://secure.gravatar.com/avatar/3a0d4408354ac7f1fddc273366daae9126187a427e91b7798e3502d2ba499b4d? s=60&d=retro&r=g) ### 󠀁[Everything done right and all design freedom. Power to FSE!](https://wordpress.org/support/topic/everything-done-right-and-all-design-freedom-power-to-fse/)󠁿 [Anne-Mieke Bovelett](https://profiles.wordpress.org/annebovelett/) 2026-يىلى 14- ئىيۇل 1 reply This works like a charm. I was set up in no time. Because the best part is that this way you have all the design freedom to make your Maintenance page look as you like it. You have all the advantages of your global styles and the ease of the Block Editor. And although there are not so many settings: read them all through well! There’s some solid SEO advice in there!Thanks a million, Troy Chaplin! ![](https://secure.gravatar.com/avatar/ad31ec5332ae89a7908ac5e4aedeb83a1d6975f9661bdeaada3c42ba86e16933? s=60&d=retro&r=g) ### 󠀁[Great plugin!](https://wordpress.org/support/topic/great-plugin-41278/)󠁿 [wpapm](https://profiles.wordpress.org/wpapm/) 2026-يىلى 9-فېۋرال 1 reply All the described features work for me. A nice, streamlined plugin. Definitely worth checking out! [ 2 باھالاشنىڭ ھەممىنى ئوقۇش ](https://wordpress.org/support/plugin/planned-outage/reviews/) ## تۆھپىكار ۋە ئىجادكار «Planned Outage for Block Themes» كودى ئوچۇق يۇمشاق دېتال. تۆۋەندىكى كىشىلەر بۇ قىستۇرمىغا تۆھپە قوشقان. تۆھپىكار * [ Troy Chaplin ](https://profiles.wordpress.org/areziaal/) «Planned Outage for Block Themes» 1 تىلغا تەرجىمە قىلىنغان. [تەرجىمانلار](https://translate.wordpress.org/projects/wp-plugins/planned-outage/contributors) نىڭ تۆھپىسى ئۈچۈن رەھمەت. [«Planned Outage for Block Themes» نى تىلىڭىزغا تەرجىمە قىلىڭ](https://translate.wordpress.org/projects/wp-plugins/planned-outage) ### ئىجادىيەتكە قىزىقامسىز؟ [كودقا كۆز يۈگۈرتۈپ](https://plugins.trac.wordpress.org/browser/planned-outage/)، [SVN خەزىنە](https://plugins.svn.wordpress.org/planned-outage/) تەكشۈرۈپ ياكى [RSS](https://plugins.trac.wordpress.org/log/planned-outage/?limit=100&mode=stop_on_copy&format=rss) ئارقىلىق [ئىجادىيەت خاتىرىسى](https://plugins.trac.wordpress.org/log/planned-outage/) گە مۇشتەرى بولغىلى بولىدۇ. ## ئۆزگىرىش خاتىرىسى #### 1.4.0 * Added scheduled outage windows with start and end date/time, entered in the site timezone * Added automatic activation/deactivation at window boundaries, evaluated on every request (no WP-Cron dependency) * Added dynamic Retry-After header during scheduled windows, reflecting the time remaining * Added schedule status to the settings page and admin bar (upcoming, active until, past window) * Added best-effort cache flushing at scheduled window boundaries via WP-Cron * Changed plugin structure: split single file into a bootstrap plus includes/ classes * Changed all admin strings to be translatable * Fixed readme requirements (WordPress 6.6, PHP 7.3) to match the plugin header #### 1.3.0 * Added uninstall hook that removes all plugin options when the plugin is deleted * Changed minimum PHP version from 7.0 to 7.3 and minimum WordPress version from 6.3 to 6.6 * Changed homepage detection to use is_front_page() and is_home() conditionals * Changed template canvas path to use the WPINC constant #### 1.2.1 * Fixed maintenance template not rendering when a static front page is set in Settings > Reading #### 1.2.0 * Added cache plugin detection with admin warning when maintenance mode is active * Added automatic cache flushing when plugin settings are saved * Added support for detecting Surge, WP Super Cache, W3 Total Cache, WP Fastest Cache, LiteSpeed Cache, and WP Rocket * Added fallback cache detection via advanced-cache.php dropin and wp-content/cache/ directory * Added no-cache headers on all bypass responses to prevent reverse proxy cache poisoning * Fixed bypass link, logged-in user, and bot responses poisoning server-level caches #### 1.1.0 * Added bypass link feature for sharing preview access with non-logged-in users * Added pre-launch mode (indefinite duration) that disables time tracking and admin warnings * Bypass link sets a 12-hour cookie for seamless navigation * Regenerate bypass link to invalidate previous links #### 1.0.0 * Initial release ## Meta * Version **1.4.0** * ئاخىرقى يېڭىلانغان ۋاقىت **7 كۈن بۇرۇن** * ئاكتىپ ئورنىتىش سانى **10 دىن ئاز** * WordPress نەشرى ** 6.6 ياكى يۇقىرى ** * **7.0.2** دا سىنالغان * PHP نەشرى ** 7.3 ياكى يۇقىرى ** * تىل * [Dutch](https://nl.wordpress.org/plugins/planned-outage/) ۋە [English (US)](https://wordpress.org/plugins/planned-outage/). * [تىلىڭىزغا تەرجىمە قىلىڭ](https://translate.wordpress.org/projects/wp-plugins/planned-outage) * بەلگە * [block-theme](https://ug.wordpress.org/plugins/tags/block-theme/)[coming soon](https://ug.wordpress.org/plugins/tags/coming-soon/) [maintenance](https://ug.wordpress.org/plugins/tags/maintenance/)[maintenance mode](https://ug.wordpress.org/plugins/tags/maintenance-mode/) * [ئالىي كۆرۈنۈش](https://ug.wordpress.org/plugins/planned-outage/advanced/) ## دەرىجە 5/5 يۇلتۇز * [ 2 5-يۇلتۇز باھالاش ](https://wordpress.org/support/plugin/planned-outage/reviews/?filter=5) * [ 0 4-يۇلتۇز باھالاش ](https://wordpress.org/support/plugin/planned-outage/reviews/?filter=4) * [ 0 3-يۇلتۇز باھالاش ](https://wordpress.org/support/plugin/planned-outage/reviews/?filter=3) * [ 0 2-يۇلتۇز باھالاش ](https://wordpress.org/support/plugin/planned-outage/reviews/?filter=2) * [ 0 1-يۇلتۇز باھالاش ](https://wordpress.org/support/plugin/planned-outage/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/planned-outage/reviews/#new-post) [بارلىق ئىنكاسنى كۆرسەت](https://wordpress.org/support/plugin/planned-outage/reviews/) ## تۆھپىكار * [ Troy Chaplin ](https://profiles.wordpress.org/areziaal/) ## قوللاش چۈشەندۈرۈشىڭىز بارمۇ؟ ياردەم لازىممۇ؟ [قوللاش مۇنبىرىنى كۆرسەت](https://wordpress.org/support/plugin/planned-outage/)