该插件尚未通过WordPress的最新3个主要版本进行测试。 当与较新版本的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.