Design : how to get an option attribute value ?

Previous topic

Developer

Next topic

Author	Message
Frédéric REITZ	Thursday 24 June 2010 5:59:55 am Hi, I've tried to add an 'options' attribute to the event class. Attribute identifier is 'category'. 3 option values added. When I fetch events and want to display ones category, I use $event.data_map.category.value. But it's empty. Also tried tyo find out where the option value could be (hell) stored. In vain. Finally decided to create a list_element class, stored my options in a folder called 'events_categories' as list_element items, then linked them as 'relation object' to events items (because relation objectS doesn't work either). I guess it's not the best method, but how should I get the option values ? data_map sub objects ? thanks for help. Fwed
Gaetano Giunta	Thursday 24 June 2010 7:23:06 am $event.data_map.category.content might be what you are looking for Principal Consultant International Business Member of the Community Project Board

Author

Message

Frédéric REITZ

Thursday 24 June 2010 5:59:55 am

Hi,

I've tried to add an 'options' attribute to the event class.

Attribute identifier is 'category'.

3 option values added.

When I fetch events and want to display ones category, I use $event.data_map.category.value. But it's empty.

Also tried tyo find out where the option value could be (hell) stored.

In vain.

Finally decided to create a list_element class, stored my options in a folder called 'events_categories' as list_element items, then linked them as 'relation object' to events items (because relation objectS doesn't work either).

I guess it's not the best method, but how should I get the option values ?

data_map sub objects ?

thanks for help.

Fwed

Gaetano Giunta

Thursday 24 June 2010 7:23:06 am

$event.data_map.category.content might be what you are looking for

Principal Consultant International Business
Member of the Community Project Board

eZ debug

Timing:	Jan 31 2025 01:25:43
Script start
Timing:	Jan 31 2025 01:25:43
Module start 'layout'
Timing:	Jan 31 2025 01:25:43
Module start 'content'
Timing:	Jan 31 2025 01:25:43
Module end 'content'
Timing:	Jan 31 2025 01:25:43
Script end

Main resources:

Total runtime	0.0265 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.0059	588.2656	151.2266
Module start 'layout'	0.0059	0.0039	739.4922	220.7188
Module start 'content'	0.0098	0.0152	960.2109	997.7422
Module end 'content'	0.0250	0.0014	1,957.9531	29.9922
Script end	0.0264		1,987.9453

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0028	10.7531	14	0.0002
Check MTime	0.0012	4.4392	14	0.0001
Mysql Total
Database connection	0.0008	3.0114	1	0.0008
Mysqli_queries	0.0027	10.3306	3	0.0009
Looping result	0.0000	0.0450	1	0.0000
Template Total	0.0010	3.7	1	0.0010
Template load	0.0007	2.6259	1	0.0007
Template processing	0.0003	1.0044	1	0.0003
Override
Cache load	0.0005	1.8215	1	0.0005
General
dbfile	0.0020	7.6903	8	0.0003
String conversion	0.0000	0.0297	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