- Optionally adds private pages to
wp_page_menu(), and the Pages widget
- Provides a separate
wp_list_private_pages()tag (a clone of
wp_list_pages()that accepts all the same arguments)
- Specifies private categories, in which all posts will automatically be set to private
- Lets you change the “Private:” prefix on private post/page titles
- Lets you change the “Protected:” prefix on password-protected post/page titles
- Lets you choose which user roles can read private pages and posts
Now on GitHub.
- French (fr_FR) by Regis Lemaire
- Bulgarian (bg_BG) by SiteGround
- Turkish (tr_TR) by Ömer Faruk Karabulut
You must have at least one public page. Otherwise, as of 3.1, the front page settings (where you can choose a static page as your home page) will not appear on the settings page at all. As long as you have one public page, all the private pages will appear as options in the dropdown menu.
Page Lists and Widgets
Adding private pages to
wp_page_menu(), and the Pages widget does not always work as it should. The private pages will be out of order, and they might appear as children of the wrong parent page. If this occurs, try using the
wp_list_private_pages() template tag instead. It’s a clone of
wp_list_pages() and should accept all the same arguments. This plugin includes an extra Pages widget that includes private pages.
When you mark a category as private, all the posts in that category will have their visibility set to private when they are published, even if you don’t change the visibility setting on the edit screen. Only published posts are affected; your draft, pending, and scheduled posts will work as usual, except that scheduled posts will be set to private when they become active.
Huge thanks to mtekk for providing the patch that makes the page list features possible. The alternative method of listing pages was adapted from Branko Ajzele.
If you would like to send me a translation, please write to me through my contact page. Let me know which plugin you’ve translated and how you would like to be credited. I will write you back so you can attach the files in your reply.
- Upload the plugin directory to
- Activate the plugin through the ‘Plugins’ menu in WordPress
Ez dago berrikuspenik plugin honentzat.
Laguntzaileak eta Garatzaileak
“Private Suite” software librea da. Ondoko pertsonek egin dizkiote ekarpenak plugin honi.Laguntzaileak
Itzul zaitez Private Suite zure hizkuntzara.
Garapena interesatzen zaizu?
Araka ezazu kodea; begira ezazu SVN biltegia, edo harpidetu garapen erregistrora RSS-(r)en bidez.
- Fixed bug where password-protected prefix field incorrectly displayed private prefix value.
- Category walker update.
- Widget constructor update.
- private, future, draft, and pending pages are now available as parents in page attributes and quick edit dropdowns
- private pages can be added to nav menus (but do not announce themselves as private, and will lead anonymous visitors to a 404 page)
- private pages can be added to page lists and widgets
- fixed uninstall hook
- fixed ‘8’ in add_options_page, argh
- updated options page to use settings API
- referred role management to Members
- fixed save_post action to avoid database call
- using mb_ereg_replace to handle multibyte strings in Private/Protected prefixes
- Turkish translation
- Bulgarian translation
- Fixed a bug involving a reference to an obsolete function. (January 3, 2011)
- Added support for custom roles.
- Fixed a problem in the way roles worked.
- Fixed bug with accented characters in title prefixes. (December 16, 2010)
- Fixed list markup when forcing private pages to appear in page lists (Thanks, Tina and Sébastien!)
- French translation by Regis (August 5, 2010)
- Fixed bug that caused conflicts with other plugins’ widgets.
- Fixed formatting of category checkboxes on the options page. (January 24, 2010)
- Fixed markup (somewhat) when adding private pages to existing template tags.
- Added private pages to parent dropdown when editing pages.
- Added page widget that includes private pages.
- Added private categories feature.
- Fixed prefix fields to work with HTML (e.g. tags)
- Translation support. (January 16, 2010)
- First release (October 15, 2009)