This container is empty

Just started with modx using v1.0.0

Have home page (id 1)with group1 page (id 2) and subgroup1 page (id 3)
Have group1user manager user with manager login startup on id 2
Group1user does not have access to id 1
When I log in as admin all is ok. When I log in as group1user I see group1 page with 3 boxes superimposed ’edit resource’ ’create resource’ and ’logout’. I do not see the ’Welcome to the content manager page’ which is what I expected.

If i click on ’edit resource’ I get the edit part highlighted in the middle of a black page which has a jagged curve in the bottom RH corner. If I user the browser back arrow I can see the content manager page but with the message ’This container is empty’

I have obviously got a wrong setting somewhere but cannot find it. I would expect /hope that group1user would see a content manager page with id2 page as his ’home’ page and showing id 3 page below it.

Can anybody help / advise please?

Thanks
Mike

Your security setup is not too clear.

Document 1 - document-group?
Document 2 - document-group?
Document 3 - document-group?

admin - administrator user-group?
group1user - role? user-group?

What are your user-group -> document-group settings?

Also, if you specify the login page to be a document, then on login the user will get that web page, not the Manager. What you are seeing is the QM+ front-end editor.

Hi Susan,

Thanks for your replies. In answer:

document 1 - resource group - wsresource
document 2 - resource group - bh1resource
document 3 - resource group - bh1resource

admin - administrator user - no group currently assigned but could go to wsgroup (admin should be able to modify all so I did not assign a group)
group1user - role content and template management - group bh1group

bh1group linked to bh1resource
wsgroup linked to whresource


Also I will want to have a user responsible for maintaining document 2 only and another user maintaining document 3 with group1user able to mantain documents 2 and 3 as a next step.


Re your second post, I understand your point but do not know how to make group1user see the content manager pointing to the tree wcontaining documents 2 and 3. Maybe I am looking for something too complicated?

When a user logs in he can only see the documents he has permissions to see. If he does not have permissions to see the parent document, then the children of that parent won’t be visible either; unless in the Configuration you enable Show Protected Pages. Then all the documents will be visible, so the user can see into the branches of the tree. He still won’t be able to open the documents he doesn’t have permissions for.

Sorry, I am wearing my stupid head today.

How can I get group1user to log in to the content manager with access to document2 and its children, in the same way that admin sees document 1 and below? I am obviously missing something fundamental here.

If you have document 2 and its children assigned to the same document group, and that document group is connected to the user group that group1user is assigned to, then he will see them and be able to edit them.

It gets complicated if you want a user to only work with the children of document 2, but not document 2 itself. Normally, if you don’t have permission to work with a document you can’t even see it or its children. That’s what the Show Protected setting does; it allows a user to see all the document, and thus their children, while they can still only edit the ones they have permissions to.

It’s the way the Tree is built; it’s sort of an all-or-nothing proposition. Actually working with a document is another process altogether.

Thank you Susan. I am going to go down the ’show protected’ route as anyone would be able to see document 2 as a web user so they will just need to accept that they cannot edit it, even though as a manager they can see it in the tree.

Having set it up, when group1user logs in he immediately sees page 2, no matter whether I set the Manager login startup to page 2 or page 1, although he can use the browser back arrow to get him to the Content Manager page. I have set the Manager Interface access to Yes.
Is this the normal scenario or have I missed a setting?

Mike

If you set a user to have a login page, he will be redirected to that page when he logs in. If you want him to go straight into the Manager, then leave that field empty.

The reason the "back" button gets him into the Manager is because it sends him back to manager/index.php, but he’s already logged in, so it just goes in to the Manager instead of displaying the login page. manager/index.php is like a switchboard; what gets displayed depends on the login status and on what actions and ids were passed in the URL.

Thank you for the explanation. I am now on the way!

I appreciate the responses, it is the first time I have used any forum on the web for support and impressed with the speed and quality of the responses so I will no doubt be back when I hit another problem

Thanks again

Mike