Forums / Setup & design / Organizing content, restricted and not restricted

Organizing content, restricted and not restricted

Previous topic

Setup & design

Next topic

Author	Message
Tore Skobba	Thursday 09 October 2003 8:51:46 am Hello all I am new with EZ and I am currently setting up an site for an Norwegian School program. This requires me to seperate content between several different user groups, and now I wonder how to best implement this functionality. My content is simplified defined as this: Content for all Content for all students Content for students studying in Singapore Content for students studying in Boston Students studying in Boston should only be allowed to gain access to content for Boston students and all students, and NOT access for Singapore content, and vica. versa. Currently I am thinking about the following solution: All content is based on content classes which are either available for all or only logged in users (restricted content). Typically I am using the following naming conventions: news_all_folder, news_restricted_folder, this is to easily allow the anonymous users (i.e. all) to get access to all none restricted material, this as I set their user role to be "read content (all classes available to all"). However, all restricted content is not to be available for all logged in user, i.e different users should get access to different restricted content based on their roles and user groups, this is to be implemented with roles to various subtrees. Does this sounds like a good way to solve it? I am having doubts about using one access solution to seperate between none and restricted content, then using another solution for sepereating restricted content. Hope someone can give some advices on this. Secondly should I use the predefined EZ content classes (article) or should I make my own in order to make future upgrades of Ez easier? cheers Tore
Alex Jones	Thursday 09 October 2003 9:02:49 am Tore, I believe the ideal solution for this case would be to use Sections to separate your content. If you create a section for each of the four categories above you could easily assign access rights to each. So, if you create two roles; one for students in Singapore and one for students in Boston you would assign both of them access rights to 'Content for all' and 'Content for al students', as well as access to the section that directly applies to them. This way you don't have to create new content classes based on their roles. Alex Alex [ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ] <i>When in doubt, clear the cache.</i>
Tore Skobba	Thursday 09 October 2003 9:16:08 am Hmm I thought section was for larger differences, such as layout etc. I am thinking about the users clicking an "News" folder. This folder then opens up into: News for anonymous News for all students News for Singapore students etc. However the site and most of the content is to be similar for all users, the only difference is that the various logged in user have access to more specific content in some folders(typically burowed down in the site). Thanks for comment Alex. I will look a bit more into sections, it might be the solution.

Author

Message

Tore Skobba

Thursday 09 October 2003 8:51:46 am

Hello all

I am new with EZ and I am currently setting up an site for an Norwegian School program. This requires me to seperate content between several different user groups, and now I wonder how to best implement this functionality. My content is simplified defined as this:

Content for all
Content for all students
Content for students studying in Singapore
Content for students studying in Boston

Students studying in Boston should only be allowed to gain access to content for Boston students and all students, and NOT access for Singapore content, and vica. versa.

Currently I am thinking about the following solution:

All content is based on content classes which are either available for all or only logged in users (restricted content). Typically I am using the following naming conventions: news_all_folder, news_restricted_folder, this is to easily allow the anonymous users (i.e. all) to get access to all none restricted material, this as I set their user role to be "read content (all classes available to all").

However, all restricted content is not to be available for all logged in user, i.e different users should get access to different restricted content based on their roles and user groups, this is to be implemented with roles to various subtrees. Does this sounds like a good way to solve it? I am having doubts about using one access solution to seperate between none and restricted content, then using another solution for sepereating restricted content.

Hope someone can give some advices on this.

Secondly should I use the predefined EZ content classes (article) or should I make my own in order to make future upgrades of Ez easier?

cheers
Tore

Alex Jones

Thursday 09 October 2003 9:02:49 am

Tore, I believe the ideal solution for this case would be to use Sections to separate your content. If you create a section for each of the four categories above you could easily assign access rights to each.

So, if you create two roles; one for students in Singapore and one for students in Boston you would assign both of them access rights to 'Content for all' and 'Content for al students', as well as access to the section that directly applies to them. This way you don't have to create new content classes based on their roles.

Alex

Alex
[ bald_technologist on the IRC channel (irc.freenode.net): #eZpublish ]

<i>When in doubt, clear the cache.</i>

Tore Skobba

Thursday 09 October 2003 9:16:08 am

Hmm I thought section was for larger differences, such as layout etc. I am thinking about the users clicking an "News" folder. This folder then opens up into:

News for anonymous
News for all students
News for Singapore students
etc.

However the site and most of the content is to be similar for all users, the only difference is that the various logged in user have access to more specific content in some folders(typically burowed down in the site).

Thanks for comment Alex. I will look a bit more into sections, it might be the solution.