Setting RootNode and UserRootNode

Previous topic

Developer

Next topic

Author	Message
Ronny Vedå	Tuesday 24 June 2003 7:40:53 am Hi I spotted the RootNode and UserRootNode settings in the content.ini [NodeSettings] # The node ID of the normal content tree RootNode=2 # The node ID of the user tree UserRootNode=5 What exactly does these settings do? At first i thought i would define what node is the root node og the document tree and user tree, but setting the RootNode to the node ID of a folder has no effect. (In the settings/override/content.ini.append file.) Nothing changes and I can still access the old root node. It would be really useful to be able to add a content.ini.append file in the siteaccess folder (is this possible?) and specify a new root node. This node would be the root when logged in from this siteaccess and the nodes above the root node would be invisible and inaccessible. The same goes for UserRootNode. When setting a user group to the new UserRootNode, only the users in this group should be accessible from this siteaccess. Does anyone know how these settings works? Ronny Vedå, Nexus Knowledge Solutions
Lachy Laycock	Tuesday 25 November 2003 1:36:27 am I have tried various ways of setting the RootNode value and in all cases so far they do not seem to have any effect. I am trying to set up a system where i can have multiple frontends with one backend and this would be the key to it's success. Any idea why this is not working? Or are we doing it wrong? Thanks.

Author

Message

Ronny Vedå

Tuesday 24 June 2003 7:40:53 am

I spotted the RootNode and UserRootNode settings in the content.ini

[NodeSettings]
# The node ID of the normal content tree
RootNode=2
# The node ID of the user tree
UserRootNode=5

What exactly does these settings do? At first i thought i would define what node is the root node og the document tree and user tree, but setting the RootNode to the node ID of a folder has no effect. (In the settings/override/content.ini.append file.) Nothing changes and I can still access the old root node.

It would be really useful to be able to add a content.ini.append file in the siteaccess folder (is this possible?) and specify a new root node. This node would be the root when logged in from this siteaccess and the nodes above the root node would be invisible and inaccessible.

The same goes for UserRootNode. When setting a user group to the new UserRootNode, only the users in this group should be accessible from this siteaccess.

Does anyone know how these settings works?

Ronny Vedå, Nexus Knowledge Solutions

Lachy Laycock

Tuesday 25 November 2003 1:36:27 am

I have tried various ways of setting the RootNode value and in all cases so far they do not seem to have any effect.

I am trying to set up a system where i can have multiple frontends with one backend and this would be the key to it's success.

Any idea why this is not working? Or are we doing it wrong?

Thanks.

eZ debug

Timing:	Jan 18 2025 15:06:52
Script start
Timing:	Jan 18 2025 15:06:52
Module start 'layout'
Timing:	Jan 18 2025 15:06:52
Module start 'content'
Timing:	Jan 18 2025 15:06:53
Module end 'content'
Timing:	Jan 18 2025 15:06:53
Script end

Main resources:

Total runtime	0.8454 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.0044	587.9219	152.6250
Module start 'layout'	0.0044	0.0025	740.5469	39.4609
Module start 'content'	0.0070	0.8369	780.0078	458.7656
Module end 'content'	0.8439	0.0015	1,238.7734	8.1563
Script end	0.8453		1,246.9297

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0031	0.3722	16	0.0002
Check MTime	0.0014	0.1647	16	0.0001
Mysql Total
Database connection	0.0007	0.0821	1	0.0007
Mysqli_queries	0.8058	95.3176	54	0.0149
Looping result	0.0005	0.0535	52	0.0000
Template Total	0.8193	96.9	2	0.4096
Template load	0.0022	0.2576	2	0.0011
Template processing	0.8171	96.6537	2	0.4085
Template load and register function	0.0001	0.0140	1	0.0001
states
state_id_array	0.0012	0.1469	1	0.0012
state_identifier_array	0.0013	0.1560	2	0.0007
Override
Cache load	0.0018	0.2129	20	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0005	0.0573	2	0.0002
Fetch class attribute name	0.0009	0.1017	2	0.0004
XML
Image XML parsing	0.0002	0.0243	2	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0018	2	0.0000
General
dbfile	0.0007	0.0792	10	0.0001
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	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 8 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs