| 开发者 | stettzy |
|---|---|
| 更新时间 | 2026年10月17日 02:54 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Yes. The standard WordPress login and administration screens remain available. Administrators always bypass the gate.
No. Knock First uses the WordPress password hashing API. The original password cannot be retrieved from the saved setting.
All existing Knock First access cookies become invalid immediately. Visitors must enter the new password.
Not when someone already knows a file's direct URL. WordPress usually serves uploaded files directly through the web server, before plugins run. Use server-level protection or private object storage when the files themselves are sensitive.
While protection is enabled, the unlock page sends no-index directives, the virtual robots.txt disallows crawling, and WordPress core sitemaps are disabled. Search engines control their own behavior, and previously indexed URLs can take time to disappear.
The plugin sends no-cache headers and sets the standard DONOTCACHEPAGE constant while enabled. Some host-level or CDN caches run before WordPress and may need a manual exclusion or cache purge.
No. It makes no remote requests and stores no visitor records. It sets one necessary HTTP-only cookie after a visitor enters the correct password.