| 开发者 | jquinn33 |
|---|---|
| 更新时间 | 2026年11月20日 14:24 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
That's expected: administrators (and the roles you choose) always see the real site. Use Preview page, or open the site in a private window.
A page cache or CDN is serving a saved copy. PJ Maintenance clears the common caching plugins when you save, but a CDN or firewall cache (such as Cloudflare or Sucuri) has to be cleared from its own dashboard.
Some scripts load their posts from the REST API without sending your login, so WordPress can't tell it's you and PJ Maintenance hides the content as it would from any visitor. Either have the script send the login cookie (in fetch(), use credentials: 'same-origin' instead of 'omit'), or untick Hide content from the REST API on the General tab.
Use Maintenance for a live site that is down for a few hours or days. Use Coming soon for a new site that hasn't launched. Use Site closed / moved when the site is shutting down and you want to point people somewhere else.
A server-level 301 redirect of the whole domain to the new site is better in that case: it passes the old site's search ranking on. Site closed is for pointing people to several places.
Click Download static page (.zip) on the General tab, back up the site, empty the site's folder, and upload the zip's contents (including .htaccess). README.txt inside the zip has the steps. The .htaccess needs Apache or LiteSpeed; the page itself works on any server.
Yes. The login page and the dashboard are never blocked. A small padlock in the corner of the page slides in a login panel (you can turn it off on the General tab). If a security plugin adds a CAPTCHA or a second step to your login, a sign-in from the panel continues on the regular login screen.
They are removed.