[SOLVED] Create Manager Users to only edit specific pages

I’ve been using modx for some time and my local lads football team have asked for a website for the entire club. This means one page per team for each team manager to edit. I’ve looked into trying to setup manager users and resource so that they can only see the page that they are allowed to edit but for the life of me I can’t seem to get it to work.

So far I have set up:

- a new manager account assigned to the Editor Role
- a new manager user group
- a new manager resource group
- linked the group with the resource
- assigned a specific page into the manager user resource

When I signed in to the manager with the new manager account I get a restricted menu across the top which I expect but I can still see and edit any of the documents in the site.

I was hoping that the document tree restricts itself to only the documents that the manager user has access to. Am I barking up the wrong tree and not really understanding the way the manager roles/permissions/groups and resources work? Or am I missing something really simple?

I’m using the latest release of modx 1.0.4

If you create a manager user and assign him to a group, then he cannot open resources that do not belong to a resource group connected to his user group. Groups determine what can be accessed, roles determine what can be done to the resources that can be accessed. So a user gets a group and a role, while resources get a group.

I would do this a bit differently. Of course, I’m not familiar with what kind of content is needed for this page, but I would use web users and the WebLoginPE snippet in Profile mode. You can have custom fields in a custom table, so just about any kind of data is manageable. Consider the team page as the team’s profile, and the team manager would be the one editing the profile. The profile editing form is totally configurable; you can insert the rich text editor or the image browser. With this method, your team managers wouldn’t go near the manager at all.

Hi sottwell,

Thanks for posting so quick. It early here and I can understand what you say but it’s taking a little while to sink in.

I’ve looked at using the front end which was my first thought but the editor removes some things I rather it woulnd’t. I can see the benefit of keeping users away from the manager and keeping things totally on the front end. I pretty reasonable when it comes to changing and writing code so I think you’ve spurred me on to something I think I can manage.

I like the use of webloginpe. Something I’ve already installed and set up to some extent. The one problem with the editor is that it has a habit or removing code from the content which I want to keep.

I’ll keep working on it and see what I can come up with.

Thanks again sottwell

Sottwell thank you so much for posting. I’ve managed to cover the little things that I need using WebLoginPE and a little change to NewsEditor Snippet.

I’ve been using WebLoginPE elsewhere in more detail but I’m amazed at its scope. A great program from Pirate and thankful it has been taken up by a group of programmers to keep it updated. Thanks all.

Here’s what I did to get around users editing a specific page.

* Created a login page with a custom field for the document id to edit
* Created a manage user page to list the users
* Created a manage user profile page so Admin can add the document id to the custom field.
* Added a new button to the successful login page which contains the custom field id. Clicking the button takes the user to the NewsEditor page pulling through the details of the page. Footer and header chunks are removed when editing but returned after submitting. The NewsEditor doesn’t save to a specific parent but saves the document back where it came from. The alias name remains unchanged.

I used PHx to remove the button from the view if a document id isn’t present.

I decided to use NewsEditor because I’d already installed it and it keeps other things it their own box.

Thanks again. You’ve been so helpful.