Sections versus Content Folders - what's the distinction?

Next topic

Author	Message
Paul Brandt	Monday 05 June 2006 6:56:54 am Hi, I'm not sure what the difference is between <i>content folders</i> and <i>sections</i>. As far as I can derive from the various documents, content folders define the site structure. At the other hand Sections "are virtual collections of nodes that belong together, either conceptually or functionally" (ref. Learning Ez Publish 3). Since a site will be designed such that its structure reflects a logical comprehension of its content, Content Folders are also collections of content (i.e. nodes) that belong together. Hence, the two concepts do not seem to differ much, at least not from the perspective that they both structure your content. The only difference I can observe is in their appliance: Where Content Folders are applied to structure the content for the sole purpose of the way the users view your website, Sections seem to be applied as a pivot between content and access rights. In other words, Sections define a content structure that is used to establish the user priviliges. Since one can assign content to belong to a section, and one can define permissions for each user or user group to sections, that effectively implies <i>who</i> is allowed to <i>act</i> on what <i>content</i>. I presume I'm correct so far. Now, when one assigns content to a section, one can select Content Folders as "start location for the section", or any other type of content one has instantiated so far. In my opinion, in this way there is no difference anymore between Sections and Content. Why not assign permissions to the content tree directly? Why this intermediary Section concept? This is making things only more complex without adding extra dynamics or logic, doesn't it? Or am I missing something? Thanks in advance for enlightening me here. Paul
Mark Marsiglio	Monday 05 June 2006 8:10:00 am We used to use sections for establishing user access rights by using section limitations on the roles. However, lately, we have found it easier to use a subtree limitation based on content for this purpose, rather than sections which require an extra step for the same outcome. The uses of sections that I think still stands out is the ability to create overrides based on sections, and the ability to assign the same section to multiple content trees. That being said, we don't use sections in most of our sites. On one that we used them on, we created a section that is only visible to logged in editors, allowing entire sub-sections of the site to be created offline, invisible to anonymous and guest users. Once the section was done, we switched the section to the standard section to make the new section visible to all users. http://www.thinkcreative.com Turning Ideas Into Strategic Solutions

Author

Message

Monday 05 June 2006 6:56:54 am

Hi,

I'm not sure what the difference is between content folders and sections. As far as I can derive from the various documents, content folders define the site structure. At the other hand Sections "are virtual collections of nodes that belong together, either conceptually or functionally" (ref. Learning Ez Publish 3).

Since a site will be designed such that its structure reflects a logical comprehension of its content, Content Folders are also collections of content (i.e. nodes) that belong together. Hence, the two concepts do not seem to differ much, at least not from the perspective that they both structure your content.

The only difference I can observe is in their appliance: Where Content Folders are applied to structure the content for the sole purpose of the way the users view your website, Sections seem to be applied as a pivot between content and access rights. In other words, Sections define a content structure that is used to establish the user priviliges. Since one can assign content to belong to a section, and one can define permissions for each user or user group to sections, that effectively implies who is allowed to act on what content.

I presume I'm correct so far. Now, when one assigns content to a section, one can select Content Folders as "start location for the section", or any other type of content one has instantiated so far. In my opinion, in this way there is no difference anymore between Sections and Content. Why not assign permissions to the content tree directly? Why this intermediary Section concept? This is making things only more complex without adding extra dynamics or logic, doesn't it?

Or am I missing something?

Thanks in advance for enlightening me here.
Paul

Mark Marsiglio

Monday 05 June 2006 8:10:00 am

We used to use sections for establishing user access rights by using section limitations on the roles. However, lately, we have found it easier to use a subtree limitation based on content for this purpose, rather than sections which require an extra step for the same outcome.

The uses of sections that I think still stands out is the ability to create overrides based on sections, and the ability to assign the same section to multiple content trees.

That being said, we don't use sections in most of our sites. On one that we used them on, we created a section that is only visible to logged in editors, allowing entire sub-sections of the site to be created offline, invisible to anonymous and guest users. Once the section was done, we switched the section to the standard section to make the new section visible to all users.

http://www.thinkcreative.com
Turning Ideas Into Strategic Solutions

eZ debug

Timing:	Jan 18 2025 15:55:41
Script start
Timing:	Jan 18 2025 15:55:41
Module start 'layout'
Timing:	Jan 18 2025 15:55:41
Module start 'content'
Timing:	Jan 18 2025 15:55:42
Module end 'content'
Timing:	Jan 18 2025 15:55:42
Script end

Main resources:

Total runtime	0.7946 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0053	589.2734	152.6563
Module start 'layout'	0.0053	0.0019	741.9297	39.5078
Module start 'content'	0.0073	0.7863	781.4375	526.3281
Module end 'content'	0.7935	0.0011	1,307.7656	12.2500
Script end	0.7946		1,320.0156

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0031	0.3903	16	0.0002
Check MTime	0.0013	0.1663	16	0.0001
Mysql Total
Database connection	0.0012	0.1509	1	0.0012
Mysqli_queries	0.7505	94.4458	54	0.0139
Looping result	0.0005	0.0578	52	0.0000
Template Total	0.7680	96.7	2	0.3840
Template load	0.0019	0.2372	2	0.0009
Template processing	0.7661	96.4153	2	0.3831
Template load and register function	0.0003	0.0325	1	0.0003
states
state_id_array	0.0010	0.1291	1	0.0010
state_identifier_array	0.0008	0.1028	2	0.0004
Override
Cache load	0.0015	0.1894	16	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0008	0.1027	2	0.0004
Fetch class attribute name	0.0010	0.1315	3	0.0003
XML
Image XML parsing	0.0026	0.3228	2	0.0013
class_abstraction
Instantiating content class attribute	0.0000	0.0014	3	0.0000
General
dbfile	0.0024	0.2983	15	0.0002
String conversion	0.0000	0.0007	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
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
3	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	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: 9 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs