Differences between related object types (Attribue Vs Normal)

Next topic

Author	Message
Bruce Morrison	Thursday 27 May 2004 1:36:35 am There seems to be a difference between a related object attribute and a the normal related object that is part of every object. For the normal related objects the variable $node.object.current.reverse_related_object_list is set which makes it possible to create a link back to the relating object(s). When you use a related object attribute this variable does not get set and there does not appear to be any way to find the relating objects without doing another fetch. I'm using 3.4 beta 2 to test this and am wondering if this is a just an issue with the beta version. If not is there any reason why the related object attribute behaves differently than the normal related objects? Cheers Bruce http://www.designit.com.au My Blog: http://www.stuffandcontent.com/ Follow me on twitter: http://twitter.com/brucemorrison Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish
Bruce Morrison	Monday 31 May 2004 9:13:23 pm I've investigated this with version 3.3-5 and the same behaviour occurs (i.e. $node.object.current.reverse_related_object_list doesn't get set for related object attributes). This behavious is consistant for both related object and related object list attributes. It would be very helpful it the related object attributes work in the same manor as the generic related object content type. I'll log this as a bug. Cheers Bruce http://www.designit.com.au My Blog: http://www.stuffandcontent.com/ Follow me on twitter: http://twitter.com/brucemorrison Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish

Author

Message

Thursday 27 May 2004 1:36:35 am

There seems to be a difference between a related object attribute and a the normal related object that is part of every object.

For the normal related objects the variable $node.object.current.reverse_related_object_list is set which makes it possible to create a link back to the relating object(s).

When you use a related object attribute this variable does not get set and there does not appear to be any way to find the relating objects without doing another fetch.

I'm using 3.4 beta 2 to test this and am wondering if this is a just an issue with the beta version. If not is there any reason why the related object attribute behaves differently than the normal related objects?

Cheers
Bruce http://www.designit.com.au

My Blog: http://www.stuffandcontent.com/
Follow me on twitter: http://twitter.com/brucemorrison
Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish

Bruce Morrison

Monday 31 May 2004 9:13:23 pm

I've investigated this with version 3.3-5 and the same behaviour occurs (i.e. $node.object.current.reverse_related_object_list doesn't get set for related object attributes). This behavious is consistant for both related object and related object list attributes.

It would be very helpful it the related object attributes work in the same manor as the generic related object content type.

I'll log this as a bug.

Cheers
Bruce http://www.designit.com.au

My Blog: http://www.stuffandcontent.com/
Follow me on twitter: http://twitter.com/brucemorrison
Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish

eZ debug

Timing:	Jan 18 2025 18:26:16
Script start
Timing:	Jan 18 2025 18:26:16
Module start 'layout'
Timing:	Jan 18 2025 18:26:16
Module start 'content'
Timing:	Jan 18 2025 18:26:17
Module end 'content'
Timing:	Jan 18 2025 18:26:17
Script end

Main resources:

Total runtime	0.8600 sec
Peak memory usage	4,096.0000 KB
Database Queries	52

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0049	588.1641	152.6563
Module start 'layout'	0.0049	0.0040	740.8203	39.5078
Module start 'content'	0.0089	0.8496	780.3281	489.0156
Module end 'content'	0.8585	0.0014	1,269.3438	12.0938
Script end	0.8600		1,281.4375

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0034	0.3946	16	0.0002
Check MTime	0.0013	0.1552	16	0.0001
Mysql Total
Database connection	0.0008	0.0909	1	0.0008
Mysqli_queries	0.8146	94.7172	52	0.0157
Looping result	0.0005	0.0602	50	0.0000
Template Total	0.8285	96.3	2	0.4142
Template load	0.0023	0.2701	2	0.0012
Template processing	0.8262	96.0630	2	0.4131
Template load and register function	0.0001	0.0090	1	0.0001
states
state_id_array	0.0009	0.1085	1	0.0009
state_identifier_array	0.0008	0.0906	2	0.0004
Override
Cache load	0.0019	0.2171	17	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0004	0.0493	1	0.0004
Fetch class attribute name	0.0009	0.1053	3	0.0003
XML
Image XML parsing	0.0004	0.0435	1	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0009	4	0.0000
General
dbfile	0.0008	0.0920	16	0.0000
String conversion	0.0000	0.0012	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/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
4	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	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: 12 Number of unique templates used: 6

Time used to render debug report: 0.0002 secs