Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

frontend: BUG on "group visible, preview for others" permission set. #334

Closed
qwerg opened this issue Sep 20, 2012 · 1 comment
Closed

frontend: BUG on "group visible, preview for others" permission set. #334

qwerg opened this issue Sep 20, 2012 · 1 comment

Comments

@qwerg
Copy link
Member

qwerg commented Sep 20, 2012

Example:
Access to a section "section-2" in this way
http://www.example.com/section-0/section-1/section-2

Protect an object setting permission: "group visible, preview for others" in various cases.
Results:


protected "document" inside a free "section-2"

• section.parentAuthorized = 1
• section.authorized = 1
• currentcontent.authorized =

correct: currentContent is not authorized


protected "section-2" (with free documents inside), inside a free "section-1"

• section.parentAuthorized = 1
• section.authorized =
• currentcontent.authorized =

correct: section is not authorized, neither currentContent


free "section-2", inside a protected "section-1"

• section.parentAuthorized = 1
• section.authorized = 1
• currentcontent.authorized = 1

uncorrect! all must be "not authorized" (NULL)


free "section-2", inside a free "section-1", inside a protected "section-0"

• section.parentAuthorized = 1
• section.authorized = 1
• currentcontent.authorized = 1

uncorrect! all must be "not authorized" (NULL)

@ghost ghost assigned batopa Sep 20, 2012
batopa added a commit that referenced this issue Sep 21, 2012
…n set

Replace !empty() with isset() to check if the "authorized" key was defined
batopa added a commit that referenced this issue Sep 21, 2012
…n set

Replace !empty() with isset() to check if the "authorized" key was defined
@batopa
Copy link
Member

batopa commented Sep 21, 2012

ok, I have fixed the bug on 3.1-ulmus and master (populus) branch
@qwerg test it, then if it's ok close the issue

@qwerg qwerg closed this as completed Sep 21, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants