Fixing Resource Creation Permissions in a Restricted Manager Role

If a manager can edit existing resources but cannot create children inside a container, the issue is usually the resource policy type, not the role rank alone.

This donor documented a very practical permissions issue: a custom manager user could see and edit a container, but could not create child resources inside it.

The working fix

The crucial adjustment was changing the resource-group access policy type from Context to Resource and making sure the policy included rights such as:

add_children, create, copy, delete, list, load, move,
publish, remove, save, steal_lock, undelete, unpublish, view

Lesson

When permissions behave asymmetrically — edit works, create does not — look closely at the specific resource policy and capability list. Role rank alone will not explain the whole behavior.

Newer post

Troubleshooting getUserDocGroups in Evolution CMS

If a documented API example does not work in your build, check the runtime context and the exact user/document scope before assuming the function is broken globally.

Older post

Limiting AjaxSearch Results to a Selected Category

If AjaxSearch falls back to the whole site when a category has no direct keyword hits, the category constraint needs to stay part of the query even in the empty-result path.