test if attribute is set

Previous topic

Developer

Next topic

Author	Message
Lauren Matheson	Friday 09 January 2004 4:13:34 pm What is the best way to test for existence of an attribute? I have been using: {section show=$MinGroup:item.data_map.link\|not} This works, but naturally ez complains: No such attribute for array(4): link Choose one of following: name, intro, body, image
Lauren Matheson	Wednesday 14 January 2004 5:38:05 pm my solution is: ... Wrong {section show=$MinGroup:item.data_map\|contains('link')} will not work because we need to test against the keys of data_map, not the values. Back to the drawing board.
Lauren Matheson	Thursday 15 January 2004 6:38:29 am Here is a solution that actually works. Apply the patch to add a keys operator, then use: {section show=$MinGroup:item.data_map\|keys\|contains(link)} The patch is filed in bug report: http://ez.no/developer/ez_publish_3/bug_reports/keys_array_operator_patch_attached Because alignment is not preserved when text is posted to the bug system, you will have to cut and paste the patch into your ezpublish implementation.

Author

Message

Lauren Matheson

Friday 09 January 2004 4:13:34 pm

What is the best way to test for existence of an attribute? I have been using:

{section show=$MinGroup:item.data_map.link|not}

This works, but naturally ez complains:

No such attribute for array(4): link
Choose one of following: name, intro, body, image

Lauren Matheson

Wednesday 14 January 2004 5:38:05 pm

my solution is: ... Wrong

{section show=$MinGroup:item.data_map|contains('link')}
will not work because we need to test against the keys of data_map, not the values. Back to the drawing board.

Lauren Matheson

Thursday 15 January 2004 6:38:29 am

Here is a solution that actually works. Apply the patch to add a keys operator, then use:

{section show=$MinGroup:item.data_map|keys|contains(link)}

The patch is filed in bug report:
http://ez.no/developer/ez_publish_3/bug_reports/keys_array_operator_patch_attached

Because alignment is not preserved when text is posted to the bug system, you will have to cut and paste the patch into your ezpublish implementation.

eZ debug

Timing:	Jan 31 2025 04:22:58
Script start
Timing:	Jan 31 2025 04:22:58
Module start 'layout'
Timing:	Jan 31 2025 04:22:58
Module start 'content'
Timing:	Jan 31 2025 04:22:58
Module end 'content'
Timing:	Jan 31 2025 04:22:58
Script end

Main resources:

Total runtime	0.0141 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.0049	588.1328	151.2109
Module start 'layout'	0.0049	0.0028	739.3438	36.6484
Module start 'content'	0.0077	0.0050	775.9922	90.0313
Module end 'content'	0.0127	0.0014	866.0234	29.9922
Script end	0.0140		896.0156

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	18.2405	14	0.0002
Check MTime	0.0010	7.3749	14	0.0001
Mysql Total
Database connection	0.0008	5.6032	1	0.0008
Mysqli_queries	0.0025	17.5709	3	0.0008
Looping result	0.0000	0.0865	1	0.0000
Template Total	0.0011	7.5	1	0.0011
Template load	0.0008	5.7524	1	0.0008
Template processing	0.0002	1.7564	1	0.0002
Override
Cache load	0.0006	4.1520	1	0.0006
General
dbfile	0.0010	6.8697	8	0.0001
String conversion	0.0000	0.0492	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