WordPress 2.7 compatible

7 Responses to WordPress 2.7 compatible

1. Kim says:

   23.12.2008 at 12:06

   Hi Andrias -

   Glad to see you working on this plugin again. It’s a lightweight, but powerful way to manage content visibility, and much easier to configure than most of the other plugins that deal with user management.

   Couple of things with the latest version that you might want to change:

   1. Position of link in admin menu: The latest version has the wpNamedUsers permissions page showing up under the Tools menu. Shouldn’t it be under the Settings menu?

   2. Minimum level for visibility of permissions link in admin menu: Currently you have this set to level 1 (Contributor). A Contributor can only write a post to submit for review (cannot publish), and is unable to edit a post after it is published. They really would have no need to mass-edit permissions, so they really shouldn’t be able to see the link. An Author (level 2), however, can edit published posts, so they should be able mass-edit permissions. I would recommend changing the level on line 57 to ’2′. This would still allow a Contributor to specify permissions when they write the article.

   BTW, I featured your plugin in a tutorial that I wrote back in November (just trying to give your project a little publicity).

   Reply
2. Andrias Sundskarð says:

   23.12.2008 at 12:12

   Hi Kim.

   I did read the tutorial that you wrote and it made me happy to see, that you bothered doing so.

   1. I did think about where to place it. I couldn’t agree with myself so I placed it under tools. The right location is probably under settings as you suggest.
   2. I will change this.

   Reply
3. brich says:

   29.01.2009 at 12:17

   Very interesting plugin. Had we known about it before, we would certainly have considered using it.

   We are building a complex website which uses WPMU and a series of linked blogs built on the same basic theme. We needed to hide content from public users in some of the blogs. The approach we took was to develop code which worked out which blog we were in and also code to detect what role the user had in the blog. We then hacked the templates to format and display content according to blog and role. It took some while to get right and a plug-in is certainly the way we would go now.

   One alternative to using groups might be to use roles and capabilities. A possible approach is to have the plug-in add default capabilities such as display title, display content, display tags, display author, display category and so on. When the plug-in is activated, these are turned off for users who are not logged in (therefore can’t see anything), and are turned on for users who have a login level (contributor, subscriber, author, editor, admin). You can then use role manager to establish new roles with selected capabilities to reflect what users in those roles can or can’t see. Now you can add a check-list of available roles to the page or post editor and control content visibility without the need to establish a new group hierarchy outside the current WordPress structure.

   Keep up the good work!

   Reply
4. Volker says:

   08.02.2009 at 16:52

   Hi,

   I tried to install the latest version of the plug-in for WordPress 2.7.

   The database tables were created successfully. The backend functionality is working and I can double-check the created content within the created database tables.

   But, as soon as I switch to the front-end or just go to “pages” in the back-end, I get ugly SQL errors. I have already tried to debug it from inside to outside.

   The most inner SQL is:
   SELECT wp2_named_users_groups_relations.group_id
   FROM wp2_named_users_groups_relations
   WHERE wp2_named_users_groups_relations.user_id =1
   which works fine.

   But:
   SELECT wp2_named_users.post_id
   FROM wp2_named_users
   WHERE wp2_named_users.user_id =1 OR wp2_named_users.group_id IN (
   SELECT wp2_named_users_groups_relations.group_id
   FROM wp2_named_users_groups_relations
   WHERE wp2_named_users_groups_relations.user_id =1
   )
   leads to the first error.

   Do you have any idea? Are there special requirements for the mysql db?

   Thanks a lot in advanced!
   Volker

   Reply
   • Andrias Sundskarð says:

     08.02.2009 at 18:20

     Please provide the detailed SQL errors.

     Reply
5. sami says:

   23.07.2009 at 17:47

   Hi–I need to allow users with the role of Author to all have access to one Post for updating. I thought this plugin accomplished this, and yet, when I assign a test user to the post, then log in as the test user, I still can’t edit the post. Can you help me? Please also reply to email address. Thank you so much!

   Reply
   • Andrias Sundskarð says:

     23.07.2009 at 18:03

     Hi, Sami.

     This plugin is not capable of doing what you want.

     Reply