Resources

My Agape try

Your Agape try


Support Forum

You must be logged in to post Login Register

Search 
Search Forums:


 




Page Associates and Page Creation

UserPost

11:43 pm
October 26, 2008


maz

Member

posts 6

1

Hi Kevin,

Thanks so much for the effort you have put into this plugin, it is fantastic! I don't think I'd be anywhere close to achieving what I want to in WordPress without it :)

Firstly, to explain the context of what I'm trying to do… I'm currently creating a company-wide intranet website, using WordPress as the CMS. The idea is that each department will have their own area of the website that they can manage. In WordPress terms, each group of users can post in only certain categories and edit/create certain pages in the page heirarchy.

Allowing the user groups to post within certain categories was simple, thanks to Role Scoper! Allowing them to edit certain pages was been a bit more tricky, but I've been able to get it working.

The main problem I'm having at the moment is trying to allow users to create subpages under certain pages. It seems from the configuration options that it maybe should be possible, but I haven't been able to figure it out! With my current configuration, users can write pages, but cannot publish them - it says the pages are pending review. Could this be due to their WP role of subscriber or something to do with the page heirarchy and drafts not being in the heirarchy? Or quite possibly I've misunderstood or misconfigured something :D

I've tried a few different combinations of configurations, but this is roughly what I have so far:

  • All users are currently set to the WordPress “subscriber” role, to give people the lowest access possible and elevate them in the specific areas (as you described in your Usage Guide :)). 
  • Users are assigned to user groups for their department. Currently I have a “post and page editing” group and a “page creation” (associate) group for each department.
  • Each “page creation” user group is set as an associate (propogating to child pages) for their department page as well as the Home (root) page (not sure if the latter is necessary, I was trying it out).
  • Each “post and page editing” group is set as an editor (propogating to child pages) for their department page (not sure whether this is relevant!)

Here's a screenshot of my current role scoper options…

It would be great if you had any insight into what I should do, or what I've done wrong! Or possibly, whether Role Scoper is capable of this :)

(sorry this is a long post!)

Cheers,

Maz

12:36 am
October 29, 2008


maz

Member

posts 6

2

I've been doing some more research into this… and it seems the issue could be related to the “Submit for Review” feature in WordPress.

WordPress currently requires pages to be reviewed if the user is not an editor or administrator, regardless of the page publishing permissions set in Role Scoper or Role Manager. It's a bit of a bummer that the option can't be turned off!

12:35 am
October 30, 2008


maz

Member

posts 6

3

Okies, I managed to get it working with the help of the Role Manager plugin, along with a lot of fiddling and testing.

For anyone who might try to achieve the same thing, here's how I configured it :)

Restricting page editing and page creation to certain site areas (page hierarchies)

Example site:

Home
- Group 1
  - Group 1 Subpage
- Group 2
  - Group 2 Subpage
- Group 3
  - Group 3 Subpage

Aim: In the above site, we want users in “Group 1″ to be able to edit the “Group 1″ page and create and edit subpages. They cannot edit any other pages in the site.

These users should ideally only see the pages they can edit in the “Manage Pages” area and in the “Page Parent” dropdown.

Instructions

WordPress configuration:

  1. Install Role Scoper and Role Manager!
  2. Create some user accounts
  3. Create the site area pages (eg. “Group 1″, “Group 2″).

Role Manager configuration:

  1. Go to Users > Roles
  2. Create (or modify an existing role) so it has the following capabilities:

    You might want to enable more capabilities, but these seem to be the minimum requirements to allow a user to publish a page without it having to be “reviewed” first (I'm not sure why!).

    Note: Click the buttons to toggle a capability… you won't see it updated until you refresh the page (at least, this was the case for me in Firefox 3).
  3. Go to Users (or Users > Authors &  Users)
  4. Assign this new role to the relevant users (be careful not to assign it to your admin account).

Role Scoper configuration:

  1. Go to “Groups” and click “add new”.
  2. Create two user groups for each site area
    - one user group for “page editors”
    - one user group for “page associates”
    (this is because you can't assign one group to be both roles - you might like to name them something like “Group 1 Page Editors”, “Group 1 Page Creators”).
  3. Click the “edit” link for your editors group and assign the relevant users to it.
  4. Repeat the above for your page associates/creators group.
  5. Edit a site area page you created before (eg. “Group 1″)
  6. Under “Advanced Options” -> “Editors”:
    - Click “show eligible groups”
    - Select your page editors group (eg. “Group 1 Page Editors”). Make sure both checkboxes are checked.
  7. Repeat the above for “Associates”, but select your page associates group (eg. “Group 1 Page Associates”).

I think that should do it!

9:55 am
October 31, 2008


Kevin

Admin

posts 2402

4

Maz,

I'm glad to hear you got this working, but you're right that the Role Manager capability changes shouldn't be necessary.  I'll look into that and let you know what I find.

Thanks for the detailed feedback!

11:54 am
November 1, 2008


Kevin

Admin

posts 2402

5

Due to some other users' editorial goals, there is a limitation that users who lack blog-wide editing capability will not see the Page Parent setting, even if they are an Editor of the page.

I added an option to turn off this limitation. (Roles > Options, "Content Maintenance" section).

This is included in the Role Scoper Beta 4 download, again slightly tweaked to beta4d (the discretionary perks of being an isolated rogue!).

3:56 pm
November 2, 2008


maz

Member

posts 6

6

Woah, fixed already? That's great!

Thanks for looking into it, and thanks SO much for this great plugin and your continued work on it :) :)


About the Agapetry forum

Currently Online:

13 Guests

Maximum Online: 150

Forums:

Groups: 2

Forums: 7

Topics: 1186

Posts: 5409

Members:

There are 1176 members

There are 1 guests


Kevin has made 2402 posts

Top Posters:

metal450 - 159

Ragnar - 105

YikYak - 70

whiteorb - 44

Daisy - 35

Administrator: Kevin | Moderators: Kevin