Sillybean

Private Suite

Allows admins to add private pages to wp_list_pages() and the Pages widget, specify the prefix on private and protected post and page titles, and choose which user roles may read private pages and posts.

Download at wordpress.org

Private Suite Options

Previous: Dashboard Notepad
Next: Next Page
24 comments

Sharing this post? The short URL is http://sillybean.net/?p=2495

24 Responses to “Private Suite”

  1. Thomas says:
    December 22, 2009 at 11:39 am

    Nice plugin, however the Site Admin in the menu of my blog formats incorrectly.

    Reply
  2. Thomas says:
    December 22, 2009 at 1:43 pm

    However i removed the extra ” on line 110 in private-suite.php and now it looks good!
    Didn’t understand why you added them though. So maybe I broke something else?

    Reply
  3. Stephanie says:
    January 12, 2010 at 9:06 pm

    Thomas, I think you’re fine. I’m reworking the plugin altogether, and hopefully the new version won’t have that issue.

    Reply
  4. Antoine says:
    January 16, 2010 at 5:18 am

    Hi, i just intalled it and let you know for infos, that at first i’d a conflict with WP-CUMULUS, that, as i’m not using it, i’ve desinstalled to avoid the common message about a “fatal error on line 305″, after that it works!

    Cheers

    Reply
  5. Jim says:
    January 20, 2010 at 3:17 am

    Version 1.0 breaks the theme. Gives me a blank page.
    Version 0.9 is still ok.

    Reply
  6. Thomas says:
    January 20, 2010 at 1:27 pm

    Jim, got a similar issue.
    Seems to be a conflict with other plugins.
    Did you look at your webservers errorlog to se what causes the error?

    Reply
  7. Seth Battis says:
    January 24, 2010 at 11:19 am

    Stephanie, the plugin looks interesting, but it conflicts with Twitter Tools. I get a PHP error in Twitter Tools with Private Suite installed that says that “aktt() widget is being redeclared by Twitter Tools”

    Reply
  8. Stephanie says:
    January 24, 2010 at 1:03 pm

    Seth, it’s not Twitter Tools, but something is going on with this plugin that’s creating conflicts with everything under the sun. I’m looking into it.

    Reply
  9. Stephanie says:
    January 24, 2010 at 1:41 pm

    I’ve just posted version 1.01. Let me know if that solves the problems!

    Reply
  10. Paul Trafford says:
    January 25, 2010 at 3:54 am

    Seems okay now – for the MHS site (WP 2.9.1) there’s no longer a conflict with the Events plugin by Arnan de Gans. Many thanks.

    Reply
  11. Thomas says:
    January 25, 2010 at 12:28 pm

    Stephanie,

    I can confirm that it seems to work fine with Countdown plugin aswell!
    Thanks!

    Reply
  12. Jim says:
    January 25, 2010 at 10:49 pm

    Version 1.0.1 fixed my problem. It’s working well now!

    Reply
  13. Amanda says:
    February 3, 2010 at 8:29 am

    Just a tip you may want to add in your directions (in case others are WP n00bs like me): You need to set the page visibility AND add the “Private:” tag.

    Reply
    • Stephanie says:
      February 3, 2010 at 12:18 pm

      Amanda, I’m not sure what you mean. Setting the visibility on the post/page edit screen is all you have to do in order to limit who sees the page. WordPress automatically adds the “Private:” prefix to those post/page titles, and this plugin allows you to change the wording.

      Reply
  14. Okoth says:
    February 18, 2010 at 2:47 am

    Just updated to Wp 2.9.2 from 2.9.
    I am using nl_NL.

    The plugin used to work in version 2.9, but not anymore after the update to WP 2.9.2.

    I want to remove ‘Private:’ so my setting is blank.

    Language issue?

    Reply
  15. Tom says:
    March 22, 2010 at 5:19 pm

    This is maybe a dumb question but how do use the plugin? :s

    I make a page private and i set some user to be able the read it in the plugin setting, but the page stays private.

    Only I, the admin, can still see it.

    Am i doing something wrong or am i forgetting something?

    Please help, i can really use this plugin. :)

    Reply
  16. belg4mit says:
    March 31, 2010 at 6:04 pm

    It looks promising, but it’s missing a few features that would really round it out… namely that the tag cloud and category listings include private pages if the user has the rights to see them.

    Reply
  17. steve says:
    April 28, 2010 at 4:14 pm

    I’ve got the same issue as Tom

    Maybe I’m missing something really obvious. I have the Private Suite options set so subscribers and above can see them. But even when I do that, any posts set to private status are now only viewable when logged in as admin!

    Tried with users that have author and editor roles and they can’t see the posts either!

    Is there some other WP setting that is conflicting here?

    TIA!

    Reply
  18. Jens Christian Larsen says:
    August 8, 2010 at 4:44 pm

    Im using private suite 1.1 on a danish WordPress 3.0.
    My issue is:
    I have a static page for frontpage and a subpage for my blog. The blogpage and another page has to be visible to logged in users only.
    The moment I set the blogpage to private, my frontpage becomes the blog and will no longer accept returning to at static page. AND the blogpage and the other private page becomes visible to not logged in users.
    Only deactivating private suite lets me put things back to order. Only the blogpage cannot be set to private.
    Kind regards.
    JCLarsen

    Reply
  19. Richard says:
    September 2, 2010 at 6:29 am

    I’m running WordPress 3.0.1 and with yout plugin activated I get errors when I update/save a page/post :

    Warning: Cannot modify header information – headers already sent by (output started at wp-content/plugins/private-suite/private-suite.php:1) in wp-includes/pluggable.php on line 890

    Besides the error, the plugin works fine.
    Any ideas?

    Reply
  20. Pierre says:
    September 6, 2010 at 12:09 pm

    Hi Stephanie,

    first of all thanks for the cool plugin !!
    I’ve noticed two things ;).
    There is a problem in the fields for “Privates posts” and “Protected posts” with accented. If i use caracter like é it becomes é. This is perhaps a problem with encoding because there are correctly saved in the option table.
    If i create a sub-category under a category that i have defined as private it is not checked as private too.
    Could you correct and implement that in the future release please ?

    TIA.

    Amicably,

    Pierre.

    Reply

Leave a Reply