| 开发者 | oversightil |
|---|---|
| 更新时间 | 2026年10月27日 05:27 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Retry-After header, which tells Google the downtime is temporary. robots.txt and sitemaps stay available.No. During a lock the site returns HTTP 503 (Service Unavailable) with a Retry-After header saying when it reopens. This is the method Google recommends for temporary closures: pages are not removed from the index and rankings are not affected. robots.txt and sitemaps keep working normally.
The admin area, the login page, the REST API, AJAX, WP-Cron and WooCommerce / payment gateway webhooks — so payments and integrations do not break.
Not by default: "Block orders during Shabbat and holidays" is on. Payment confirmations (webhooks) for orders started before Shabbat, orders created by an administrator, and the WooCommerce REST API (/wc/v3) are not blocked.
Yes. The plugin purges the page cache when each lock starts and ends (WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, SiteGround Optimizer, WP Fastest Cache, Breeze, Cache Enabler, Nginx Helper). In addition, a small script on every page checks the lock state and shows the lock page even if an old cached page was served.
On fully cached sites we recommend a real server cron so the purge runs on time, for example */5 * * * * curl -s https://example.com/wp-cron.php?doing_wp_cron > /dev/null, together with define( 'DISABLE_WP_CRON', true ); in wp-config.php.
The Cloudflare cache is not purged automatically. If you cache HTML pages on Cloudflare (Cache Everything / APO), exclude the site or purge manually. Developers can hook their own purge into the oversight_shabbat_purge_cache action.
Some servers replace every 503 response with their own error page. Ask your host not to intercept 503 responses from the site.
Yes. The Hebrew (he_IL) translation is delivered through translate.wordpress.org; on a Hebrew site the admin screens and the lock page are shown in Hebrew, right-to-left.