The resources listed in the error messages must be protected somehow in the context that the code calling the processor is running under and/or the current user is not logged in to the current context.

Hm. I dont get it right done.
I had one ressource group and one element category, assigned to a admin group with level 0. User 10, level 10, is is not in that group and has minor privileges. ACLs where working before upgrade.

Clicking ressources in the ressources tree give the prompt, even if they a not in the log. Closing the prompt lets me edit the ressource, logged as user 10. So the the promt is triggered by the tree at the left and not the ressource that is in the editor?

I had no success by configuring the ressource group, so I deleted it for know. The log now lists only problems with modCategory. Did I take the basic concept of ressource groups and categorys wrong? My expectation was: assigning a ressource group to a user group should hide the ressources for other user groups with less privileges.

Update: I also removed the element category. There is no modCategory entry in the log any more. But the promt is still there.
[ed. note: spica8 last edited this post 3 months, 3 weeks ago.]

My expectation was: assigning a resource group to a user group should hide the resources for other user groups with less privileges.

That's close. Assigning a resource group to a user group hides the resources from all users who are not in the user group when the context specified in the ACL entry is the current context. If the context of the ACL entry is 'mgr' it will hide nothing when users are in the front-end ('web' context).

In the end it was just one single permission: view_template
Checking solved it.
It was needed to show the template dropdown in the ressource.
Dont know, why the permission was handled differently after the upgrade. Only try and error let me find it.

I am the administrator on the system and logged in as such. I have tried to select the folder properties and unchecked the read only box but the files remain read only! I have several important excel workbooks that I access daily and the only way I can edit them right now is to move them out of the document folder and leave them on the desktop!
How can I restore write permissions within these folders and the contents firstpremiercard login?
[ed. note: willne225 last edited this post 3 months ago.]