Multiple object locations under the same parent

Next topic

Author	Message
Piotrek Karaś	Tuesday 11 March 2008 10:00:48 pm What consequences do you expect from allowing an object to have multiple locations under the same parent node? I've just played with locations a bit and bypassed some restrictions and it seems to work (nodes have the same name, but different URLs): # Parent node (ID:1, object ID:1, URL: parent_node) ## Node (ID:2, object ID:2, URL: parent_node/node) ## Node (ID:3, object ID:2, URL: parent_node/node2) ## Node (ID:4, object ID:2, URL: parent_node/node3) ... Should I expect any tree disaster? ;) BTW. I'm not planning to use this in a production env ;) -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu
Piotrek Karaś	Monday 14 April 2008 10:05:04 am No volunteers for abstract problems? ;) -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu
Kristof Coomans	Tuesday 15 April 2008 12:13:16 am Hi Piotrek With which reason would you want to do this? :) independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org

Author

Message

Tuesday 11 March 2008 10:00:48 pm

What consequences do you expect from allowing an object to have multiple locations under the same parent node? I've just played with locations a bit and bypassed some restrictions and it seems to work (nodes have the same name, but different URLs):

# Parent node (ID:1, object ID:1, URL: parent_node)
## Node (ID:2, object ID:2, URL: parent_node/node)
## Node (ID:3, object ID:2, URL: parent_node/node2)
## Node (ID:4, object ID:2, URL: parent_node/node3)
...
Should I expect any tree disaster? ;)
BTW. I'm not planning to use this in a production env ;)

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

Piotrek Karaś

Monday 14 April 2008 10:05:04 am

No volunteers for abstract problems? ;)

Kristof Coomans

Tuesday 15 April 2008 12:13:16 am

Hi Piotrek

With which reason would you want to do this? :)

independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org

eZ debug

Timing:	Jan 18 2025 19:37:08
Script start
Timing:	Jan 18 2025 19:37:08
Module start 'layout'
Timing:	Jan 18 2025 19:37:08
Module start 'content'
Timing:	Jan 18 2025 19:37:08
Module end 'content'
Timing:	Jan 18 2025 19:37:08
Script end

Main resources:

Total runtime	0.0325 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0164	589.1797	152.6406
Module start 'layout'	0.0164	0.0051	741.8203	39.4766
Module start 'content'	0.0215	0.0088	781.2969	93.3672
Module end 'content'	0.0303	0.0022	874.6641	34.3047
Script end	0.0325		908.9688

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	8.2363	14	0.0002
Check MTime	0.0011	3.5326	14	0.0001
Mysql Total
Database connection	0.0023	7.1318	1	0.0023
Mysqli_queries	0.0101	31.0777	3	0.0034
Looping result	0.0000	0.0894	1	0.0000
Template Total	0.0017	5.3	1	0.0017
Template load	0.0010	3.0980	1	0.0010
Template processing	0.0007	2.1980	1	0.0007
Override
Cache load	0.0007	2.2221	1	0.0007
General
dbfile	0.0003	0.9381	8	0.0000
String conversion	0.0000	0.0366	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	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs