| 开发者 | kirkclarke |
|---|---|
| 更新时间 | 2026年9月28日 13:31 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Turn on "Hide Prefix" in the settings.
The same "Hide Prefix" setting controls both the private and protected prefix.
Yes — leave "Hide Prefix" off and set your own text in the Private Title Prefix / Protected Title Prefix fields.
The Protected Intro Text, Protected Label Text, and Protected Button Text fields cover the form itself; Invalid Password Text covers what shows after a wrong attempt.
Go to Settings > Private & Protected instead. It has every option the Customizer has, and edits the same values.
Yes — the prefix comes from the same title WordPress uses everywhere, so menus, widgets, and the browser tab all update along with the page's own heading.
No. It only changes how WordPress's own built-in "Password Protected" and "Private" post visibility options look — you still set those from the post/page editor's Visibility setting.
Yes — turn on "Use Default Form" and the plugin hands off to Divi's own password form (still adding the widget areas around it).
Turn on "Hide From Lists." The post is still reachable at its own URL; it just won't appear in listings. (Private posts are already hidden from anyone who can't view them.) Something not covered here? Ask in the support forum — it's the fastest way to reach me.
aria-describedby; screen readers now announce it.git directory (full commit history) into the public SVN repository, because .distignore never listed .git. Purged and fixed; no secrets were ever in that historyis-protected/is-private body classes and the frontend stylesheet no longer apply to archive pages just because the first listed post happens to be private or protectedaria-describedby attribute, which was also outputting a bare unwrapped ID instead of a real attribute% character in a custom title prefix no longer breaks the page on PHP 8class attribute, so theme styles for .post-password-form apply again