Titanium Service Zones – Maintenance Mode, Coming Soon & Page Control
| 开发者 | aplugins |
|---|---|
| 更新时间 | 2026年8月27日 23:50 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
/checkout/, or a trailing-wildcard path such as /account/*. Each zone can be Operational, show a non-blocking Service Notice, or return a proper temporary-unavailable Maintenance response.
Before activating a zone, use Impact Preview and Safety Check to see known matching WordPress Pages and review broad, critical, or transaction-related routes. The Conflict Detector identifies overlapping zones and explains the deterministic priority rule. More-specific targets win, so an Operational child zone can deliberately keep a smaller area live inside a broader maintenance path.
Titanium Service Zones also keeps the original whole-site controls for situations where the complete website really should change at once: Normal, Visitor Service Notice, Coming Soon, or Maintenance Mode.
Service Zones included in Free
- Up to three independent Service Zones
- WordPress Page or URL-path targeting
- Exact paths and trailing
*path prefixes - Operational, Service Notice, or Maintenance state per zone
- Zone-specific visitor title and message
- Proper HTTP 503 response for zone maintenance, including Retry-After and no-cache/search-engine headers when headers can still be sent
- Maintenance Impact Preview for known published WordPress Pages
- Built-in Safety Check for very broad, protected WordPress, account, checkout, payment, callback, and similar sensitive-looking routes
- Zone Conflict Detector for overlapping targets
- Deterministic specificity priority; more-specific targets win and equal targets use the earlier zone
- Operational exceptions inside broader Service Notice or Maintenance paths
- Optional automatic public Service Status page at
/service-status/ - Optional read-only JSON status endpoint at
/wp-json/titanium-service-zones/v1/status - Public status output exposes zone names and states, not private target paths or internal rules
- Normal, Visitor Service Notice, Coming Soon, and Maintenance Mode states
- Proper HTTP 503 whole-site maintenance response with Retry-After
- Separate indexable HTTP 200 Coming Soon page
- Four ready-made service notices for hosting, performance, feature, and service interruptions
- Separate Coming Soon and maintenance titles, messages, logos, background colours, accent colours, and optional login buttons
- Custom internal login path such as
/login; the exact page stays accessible while the login button is enabled - Independent administrator frontend access and wp-admin reminder visibility
- Responsive public output and a clear light/dark WordPress admin interface
- Cache-purge integrations for LiteSpeed Cache, WP Rocket, WP Super Cache, and W3 Total Cache
- Verified settings rollback, shared Free/Pro data, and bounded multisite lifecycle and cleanup
- Up to 500 reusable Custom Notices with separate headings and messages
- Start/end dates, weekdays, daily time windows, overnight schedules, and WordPress-site timezone handling
- Optional schedule countdown that reloads the page when maintenance ends
- Up to 1,000 validated conditions using AND inside groups and OR between groups
- Login-state, standard/custom role, and WordPress capability targeting
- Specific pages, posts, public custom content, front page, posts page, blog home, search, 404, singular content, and archives
- Post-type archives, taxonomy archives, and specific taxonomy terms
- URL-path, query-parameter, mobile/desktop, and browser targeting
- WooCommerce shop, product, cart, checkout, My Account, account endpoints, product categories/tags, specific products, purchased products, and active subscription products
- Paid Memberships Pro, MemberPress, WooCommerce Memberships, Restrict Content / Pro, Paid Member Subscriptions, LifterLMS, and LearnDash course/group targeting
- Supported active, inactive, expired, cancelled, pending, paused, trial, complimentary, delayed, changed, abandoned, and other recorded membership states where the integration provides them
安装:
- Upload and activate Titanium Service Zones.
- Open Service Zones > Settings.
- Keep Whole-Site Status set to Normal when you want selective Service Zones to control only part of the website.
- Configure up to three zones using a WordPress Page or URL path, then choose Operational, Service Notice, or Maintenance.
- Use Preview Impact & Safety before activating a new path rule and review any overlap warning.
- Optionally enable Automatic Public Service Status to publish
/service-status/and the read-only JSON status endpoint. - Use Whole-Site Status when the entire website should show a Visitor Service Notice, Coming Soon page, or Maintenance Mode page.
- Save the settings and use a private browser window when comparing the visitor view.
屏幕截图:
常见问题:
What is a Service Zone?
A Service Zone is one selected part of the public site. It can target one WordPress Page, an exact URL path, or a trailing-wildcard path prefix. That zone can remain Operational, show a Service Notice, or return an HTTP 503 Maintenance page while unrelated site areas remain online.
How many Service Zones are included in Free?
Three. The shared Free core in both editions uses the same three-zone system.
What happens when two zones overlap?
The more-specific target wins. A Page target outranks path rules, an exact path outranks a wildcard prefix, and a longer wildcard prefix is more specific than a shorter one. If specificity is equal, the earlier zone wins. This also lets an Operational zone create a live exception inside a broader maintenance path.
What does Impact Preview show?
For saved WordPress Pages, the preview shows known published Pages that match the selected target. URL paths can also match dynamic endpoints that are not stored as WordPress Pages, so the interface clearly notes that the preview is not a complete crawler of every possible runtime URL.
What does the Safety Check do?
It warns about extremely broad patterns, protected WordPress routes, and transaction/account-looking paths such as checkout, payment, webhook, callback, cart, or My Account routes. WordPress admin, login, REST, AJAX, cron, and XML-RPC requests are intentionally protected from Service Zone blocking.
Does a Maintenance Zone return HTTP 503?
Yes. A matched Maintenance Zone returns HTTP 503 with Retry-After and noindex/no-cache handling when WordPress can still send headers. Unaffected URLs continue to use their normal responses.
Can I still use whole-site Maintenance Mode or Coming Soon?
Yes. Whole-Site Status remains available. When it is anything other than Normal, it takes priority and Service Zones stay saved but do not independently affect visitors.
Can administrators still access the website?
Yes. The existing administrator visibility setting applies to the public runtime. When administrator application is disabled, administrators can work on the frontend without receiving the public maintenance replacement.
What is Automatic Public Service Status?
When enabled, Titanium Service Zones generates a read-only /service-status/ page and JSON endpoint from Whole-Site Status and the configured zone states. It publishes zone names and state labels only; target paths and matching rules are not exposed.
What happens when the plugin is deactivated?
The lifecycle process returns Whole-Site Status to Normal and resets configured Service Zones to Operational while preserving their definitions. Supported page caches are purged when a public state had been active.
Does it work with page caching or a CDN?
The plugin marks eligible Service Zone, Coming Soon, maintenance, and service-notice responses as non-cacheable and purges supported WordPress page caches after relevant state changes. Server-level caches, reverse proxies, and external CDNs can serve content before WordPress runs, so their own purge controls may still be required.
更新日志:
- Initial release.