這個外掛並未在最新的 3 個 WordPress 主要版本上進行測試。開發者可能不再對這個外掛進行維護或提供技術支援,並可能會與更新版本的 WordPress 產生使用上的相容性問題。

FT Password Protect Children Pages

外掛說明

This plugin does one thing. If a page that is password protected has children pages, all children pages will be protected with the same password.

If the correct password is entered on the parent page or any of its children pages, all related pages will be viewable to the user.

The plugin protects unlimited levels of grandchildren pages via the $post->ancestors. It uses first ancestor that is password protected.

Additional Information

The plugin currently works by looking for parent pages that are password protected and applying the same restrictions the the currently being viewed child page. This means that the children pages do not actually get a password added to the database.

I’m trying to decide if this is the best way to proceeed or if I should take another route (such as adding / updating / removing passwords from children pages at the write or save post screen).

Please feel free to offer any suggestions or report any bugs here: [http://fullthrottledevelopment.com/password-protect-children-pages/]

Thanks!

安裝方式

Upload the plugin to your plugins directory then activate it.

Ask Questions here: [http://fullthrottledevelopment.com/password-protect-children-pages/]

使用者評論

2019 年 12 月 28 日
Not only does it automatically protect the children pages, but it only requires your visitors to enter the password ONCE at the parent level. My children pages are coded as Visibility: Public, and it STILL protects them. I don't have to enter a password for every single one. This is AMAZING! Why does this plugin not have more reviews?!
閱讀全部 4 則使用者評論

參與者及開發者

以下人員參與了開源軟體〈FT Password Protect Children Pages〉的開發相關工作。

參與者

變更記錄

0.3

  • Fixed bug where children pages of non-protected parents had ‘Protected: ‘ prepended to the title.
  • In case where grandparent page is not protected but parent page was, child pages are now protected.

0.2

  • Added ability to protect all levels below initially protected page. Props to trevorgehman on the WP.org support forums for the tip.