Linux 软件免费装
Banner图

Gatekeepr – Password Protect for Post Types

开发者 mbilalkk
更新时间 2026年7月29日 23:52
PHP版本: 7.4 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

custom post type access control content protection restrict content password protect

下载

1.0.0

详情介绍:

Gatekeepr lets you require a password before visitors can view the single/detail page of any post type — Posts, Pages, or any custom post type registered by your theme or another plugin. Unlike WordPress's built-in per-post password protection, this plugin protects an entire post type at once from a single settings screen — with either one shared password for everything, or an individual password per post type. Features Development happens in the open on GitHub: https://github.com/bilalkk9/post-type-password-protect A note on the "current password" display The Gatekeepr settings screen can show you the current password (hidden by default, behind a "Show" toggle) so you don't need to reset it if you've forgotten it. To make this possible, the password is stored in an encrypted, recoverable form rather than only as a one-way hash. If your workflow requires a password that can never be viewed after saving, simply treat the field as write-only and don't use the "Show" toggle — the underlying visitor-facing verification always uses a one-way hash regardless.

安装:

  1. Upload the plugin files to the /wp-content/plugins/gatekeepr directory, or install the plugin directly through the WordPress "Plugins → Add New" screen.
  2. Activate the plugin through the "Plugins" screen in WordPress.
  3. Go to Settings → Password Protect.
  4. Check the post types you want to protect, set a password, and click "Update Password".

屏幕截图:

  • The appearance settings — background color, accent color, logo, and secondary button.
  • The front-end unlock screen shown to visitors.

常见问题:

Does this replace WordPress's built-in post password feature?

No. WordPress's native feature protects one post at a time with a password you set per-post. This plugin instead protects every single/detail page of a chosen post type at once, from a single settings screen — with a shared password across all protected types, or a separate password for each one.

Will search engines index my protected pages?

No. While a page is locked, the unlock screen is served with a noindex directive instead of the real content.

What happens if I change the password?

Every visitor who was previously unlocked will be asked for the password again on their next visit. This happens automatically — there is nothing to clear manually.

Does this work with page builders like Elementor?

Yes. The gate runs before the page is rendered, so it works regardless of how the page itself was built.

Does this affect the REST API or RSS feeds?

Protected, locked posts have their content and excerpt redacted in both the REST API and RSS/Atom feed output, so the underlying content isn't exposed through those either.

更新日志:

1.0.0