Organizing content, restricted and not restricted

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

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.

eZ debug

Timing:	Jan 19 2025 01:00:28
Script start
Timing:	Jan 19 2025 01:00:28
Module start 'layout'
Timing:	Jan 19 2025 01:00:28
Module start 'content'
Timing:	Jan 19 2025 01:00:29
Module end 'content'
Timing:	Jan 19 2025 01:00:29
Script end

Main resources:

Total runtime	0.7377 sec
Peak memory usage	4,096.0000 KB
Database Queries	57

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0071	589.3047	152.6406
Module start 'layout'	0.0071	0.0114	741.9453	39.4766
Module start 'content'	0.0185	0.7177	781.4219	535.6797
Module end 'content'	0.7362	0.0014	1,317.1016	12.1250
Script end	0.7376		1,329.2266

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0036	0.4935	16	0.0002
Check MTime	0.0013	0.1786	16	0.0001
Mysql Total
Database connection	0.0009	0.1231	1	0.0009
Mysqli_queries	0.6696	90.7709	57	0.0117
Looping result	0.0005	0.0730	55	0.0000
Template Total	0.6887	93.4	2	0.3443
Template load	0.0027	0.3722	2	0.0014
Template processing	0.6859	92.9847	2	0.3430
Template load and register function	0.0002	0.0283	1	0.0002
states
state_id_array	0.0004	0.0547	1	0.0004
state_identifier_array	0.0008	0.1091	2	0.0004
Override
Cache load	0.0023	0.3071	30	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0009	0.1256	2	0.0005
Fetch class attribute name	0.0018	0.2446	4	0.0005
XML
Image XML parsing	0.0006	0.0865	2	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0014	4	0.0000
General
dbfile	0.0074	1.0017	16	0.0005
String conversion	0.0000	0.0015	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
6	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
3	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 15 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs