Alias in Global Scrapbook - Access denied

Permalink
Short way:
I'm using Advanced Permissions and I have to share some content across site, which should be editable for Editors group. Probably I'm missing some Scrapbook permissions here, because when user in Editor group tries to edit shared block, which is alias to Global Scrapbook, he gets "Access denied".

In more details:
First I logged in as admin, made Content block to footer area and copied it to Global Scrapbook as alias. Then I went to Page Type => Defaults and added that block from Global Scrapbook to footer area and set it to all child pages.

By using admin user everything works like a charm. When I edit that shared block on any page it says "This is a global block. Editing it here will change all instances of this block throughout the site." which is exactly what I want. However, editors can't edit that block. They can delete or even add it from Global Scrapbook, make some other blocks and edit them, but they just can't edit any content in Global Scrapbook.

How to set permissions there?

orisinal
 
Tony replied on at Permalink Reply
Tony
not 100% sure this will work, but try going to the sitemap, turn on the system pages checkbox on the right so you can see the dashboard pages, find the global scrapbook page, and set the permissions for it to be less restrictive, like giving the Editors group read, and maybe right access. please let me know if that worked too.
orisinal replied on at Permalink Reply
orisinal
That came to my mind before my post, but I didn't find any other scrapbook page than the Scrapbook (no Shared or Global Scrapbook inside it). So I did a little test and gave same permissions as Administrators group have (read, write, admin) to Scrapbook, but I didn't see any difference.

(Btw, would be nice feature here if we could see monitoring status of commented users...or maybe not, as people may start to send unnecessary private messages, dunno)
Tony replied on at Permalink Reply
Tony
yeah, this seems like a bug. can you please add it to the bug tracker, and hopefully it'll be taken care of in the next release of concrete.
orisinal replied on at Permalink Reply
orisinal
Oh, I found this same issue from the bug tracker. Didn't find that earlier. Not as detailed as this post, but exactly same problem.

http://www.concrete5.org/index.php?cID=26635...
meir replied on at Permalink Reply
I cannot access the bug page, can you please post the solution to the problem?
orisinal replied on at Permalink Reply
orisinal
I wasn't able to find the same bug report, but probably most related and the problem you have now is this one:

http://www.concrete5.org/developers/bugs/5-4-1-1/access-denied-on-g...
meir replied on at Permalink Reply
Clearing the cache doesn't help.
What did you do?
orisinal replied on at Permalink Reply
orisinal
I'm not sure if I remember this problem/solution right, but I think that my Editors group didn't have permissions to access the Dashboard. Giving permissions to access the Scrapbook doesn't have any effect if user doesn't have access to Dashboard.

Therefore I made a group "Dashboard" and gave it access to the dashboard but nowhere else inside Dashboard (umm, maybe to Sitemap, too). Then I added all the users into the Dashboard group and editor users were also in the Editors group. I'm pretty sure this solved my problem.

If someone can confirm my solution or give better one, please tell us! :)

EDIT: Oh, and this has nothing to do with the bug report I just referred. I just didn't remember this original problem/solution at first :)
meir replied on at Permalink Reply
This didn't help. The weird thing is that it only does not work for the content block. all other blocks work perfectly.