Area Permissions

Permalink
I try to search around the forum but i found nothing.

I'm using Concrete 5.2RC2 with advanced permissions enabled.

I setup my page type defaults by setting permissions in areas for restricting access to a specific group.
The problem is that when i create a new page the area permission isn't copied from the page default.

Anyone have the same problem?
It's a bug or my fault?

Thanks.

drugo
View Replies:
andrew replied on at Permalink Reply
andrew
Could you describe this in a little more detail? What are the permissions on the newly created page? What are the permissions on the page the newly added page was added to ?

If you go into the dashboard, sitewide settings, and click "clear cache" do the permissions appear to filter down to the area appropriately ?
drugo replied on at Permalink Reply
drugo
Perfect, cleared the cache all goes right, even pages already created take the right permission. Great!

Thanks a lot.

C5 is the best CMS i ever seen and my web agency subsbribe soon to the partners program.
drugo replied on at Permalink Reply
drugo
I do some extensive test and i found the problem.
I try to explain.

I created a page default with specific permission for a group. This group can do all except "admin". The page default have 3 areas. The group have edit pemission only on one of the 3 areas, the others areas is read only.
If a user of this group add a new page of this type, just the page is created he see the page with correct permissions, so with only content area editable and the others 2 read only, but when he save the page and re-open it, or even when he edit or add content to the page before saving it for the first time, all the areas on page lose the specific permissions and take full access.
General page permissions stay correct instead.
Then, if the admin clear the cache, all the permissions back correct, but it can be late and the user may edit where it should not.

I hope this explanation is more clear than previous, my english isn't perfect ... :)
andrew replied on at Permalink Reply
andrew
I will add this to our list of bugs to fix that are a high priority.

Out of curiosity, could you upgrade to full 5.2 and see if this bug still exists? We've done quite a bit of work on fixing cache related bugs over the past few weeks and this one may be one of those (since I noticed area permissions problems at some points in the past, too, that I think we've addressed.)
drugo replied on at Permalink Reply
drugo
Just tried 5 minutes ago, but the problem persists.
drugo replied on at Permalink Reply
drugo
In 5.2.1 this problem is solved!

Thanks!