We just spent two hours achieving the above goal. The hard part allowed anonymous users on the front panel to view the Menu Widget , but not see or access the new type of Protected Page .
Our solution works.
- Anonymous users can view the menu widget .
- Anonymous users can view links to content links to pages in widgets .
- Anonymous users cannot view the Content links. Links to Protected Pages in the Menu Widget.
- Anonymous users can view user links to something in the main menu.
- Anonymous users are requested to authenticate if they directly go to the Secure page .
- All this is good.
What we are interested in is “is there a better way?” and "What do I need to set permissions both at the content type level and on the widget instance for the menu widget?"
First we created a new content type for the secure page. Then we set the following permissions.
Users> Roles (view and access permissions)
Anonymous Authenticated
View page by others y y n y
View own page y y n y
View projection by others y y n y
View own projection y y n y
View secure page by others n n n y
View own secure page n n n y
View all content n n y y
View own content n n n y
View content types n n n n
Access site front end y y y y
/ , ; View . , , / , , .
, View/ , . , Content Permission Menu .
> >
Anonymous Authenticated
View any content n y y n
View own content n n y n
, . :
> >
Disable this (i.e. unchecked it)
Otherwise it overrides what we already set.
.
: , . , ?