How to fetch attributes of a node

Previous topic

Developer

Next topic

Author	Message
Ashwini V	Thursday 03 March 2005 9:26:01 pm Hi, I need to fetch a attribute sys_admin from the folder class. I have entered the data for this attribute, however, I am not able to fetch the data. I am using $node.data_map.sys_admin.data_text to fetch the content. But this doesnt return anything? I had designed the class in 3.2 version. This code is working fine in 3.2 site, but it doesnt return anything in 3.5. How can I fetch the value of this attribute? Thanks Ashwini
Łukasz Serwatka	Thursday 03 March 2005 10:04:13 pm Hi Karthik, You can use attribute_view_gui For example: {attribute_view_gui attribute=$node.object.data_map.sys_admin} To view all attributes of current node you can use {$node\|attribute(show)} Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
Eirik Alfstad Johansen	Thursday 03 March 2005 10:08:51 pm Hi Karthik, I too have experienced template code that has stopped working due to an upgrade to 3.5. So far, it has either been caused by an error in the template syntax (like a missing {/let}), or that I've used $node.object.data_map (when I changed to $node.datamap, it has worked). Sincerely, Eirik Alfstad Johansen http://www.netmaking.no/

Author

Message

Ashwini V

Thursday 03 March 2005 9:26:01 pm

Hi,

I need to fetch a attribute sys_admin from the folder class. I have entered the data for this attribute, however, I am not able to fetch the data. I am using $node.data_map.sys_admin.data_text to fetch the content. But this doesnt return anything? I had designed the class in 3.2 version. This code is working fine in 3.2 site, but it doesnt return anything in 3.5. How can I fetch the value of this attribute?

Thanks
Ashwini

Łukasz Serwatka

Thursday 03 March 2005 10:04:13 pm

Hi Karthik,

You can use attribute_view_gui

For example:

{attribute_view_gui attribute=$node.object.data_map.sys_admin}

To view all attributes of current node you can use
{$node|attribute(show)}

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

Eirik Alfstad Johansen

Thursday 03 March 2005 10:08:51 pm

Hi Karthik,

I too have experienced template code that has stopped working due to an upgrade to 3.5. So far, it has either been caused by an error in the template syntax (like a missing {/let}), or that I've used $node.object.data_map (when I changed to $node.datamap, it has worked).

Sincerely,

Eirik Alfstad Johansen
http://www.netmaking.no/

eZ debug

Timing:	Jan 31 2025 04:33:24
Script start
Timing:	Jan 31 2025 04:33:24
Module start 'layout'
Timing:	Jan 31 2025 04:33:24
Module start 'content'
Timing:	Jan 31 2025 04:33:24
Module end 'content'
Timing:	Jan 31 2025 04:33:24
Script end

Main resources:

Total runtime	0.0132 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0039	588.1406	151.2109
Module start 'layout'	0.0039	0.0027	739.3516	36.6641
Module start 'content'	0.0066	0.0051	776.0156	90.2813
Module end 'content'	0.0118	0.0014	866.2969	33.9922
Script end	0.0132		900.2891

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0022	16.8907	14	0.0002
Check MTime	0.0010	7.9352	14	0.0001
Mysql Total
Database connection	0.0005	3.7334	1	0.0005
Mysqli_queries	0.0024	18.4571	3	0.0008
Looping result	0.0000	0.1049	1	0.0000
Template Total	0.0011	8.1	1	0.0011
Template load	0.0008	6.2657	1	0.0008
Template processing	0.0002	1.7835	1	0.0002
Override
Cache load	0.0006	4.3683	1	0.0006
General
dbfile	0.0010	7.2588	8	0.0001
String conversion	0.0000	0.0579	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