Can't add Resource access policy in Context Access

Yes, it looks like the Resource Policy was selected before MODX enforced the distinction. I'm not sure what the side-effects of having that selected might be.

The default ACL entries, created by MODX on a fresh install, are here: http://bobsguides.com/default-acl-entries.html.


Since the users in your groups are all equal, their Role doesn't really matter. The main function of Roles in Revolution (unlike Evolution) is to give users in the same User group different capabilities. I would use some arbitrary role rather than Super User just because it would give me more flexibility in the future and prevent possible security problems if I forget that they're all Super Users down the road.


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

Yes, thanks for all the feedback Ray. Probably a function of the upgrade from 2.0.7 to 2.0.8 is why the sudden change for my users. In any case, I'm a techie turned marketing guy, so nice to use my brain on this for a change (among the many hats I have to wear at a small company).

Thanks for all the help (again). You rock!

Bingo!!! Figured it out.

The Content Editor policy has publish / unpublish rights - and somehow this was turned OFF. Turned it back on and bingo, by Blog posters and HR users can now publish.

I believe in the old setup, my contractor tried to use Resource Policy (which also has publish / unpublish) to control this.

Problem solve. And I don't need the custom Publisher Policy I created.

Sounds good.

The Resource Policy wouldn't work in the Context Access ACL entry because it would give the user 'publish' permission but not 'publish_document' permission. The user needs both for protected resources and would only have the first one (that's one reason why the Resource Policy no longer shows up for Context Access ACL entries).

In fact, without 'publish_document' permission, the user can't publish any documents, protected or not.

I think the 'publish' permission is left out of the ContentEditor Policy on the assumption that someone higher up will be reviewing the resources before publishing them.


I'm glad you got it sorted. Thanks for reporting back.


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html