Wash of unwanted zeroes

Previous topic

Setup & design

Next topic

Author	Message
Olav Bringedal	Wednesday 02 February 2005 6:20:53 am Heya I got a class that got 20 fields of integer. In the view template I'd like every value that's not 0 to show as blank. I tried rewriting the wash method with adding a "notzero" attribute, but that's not a slick solution at all. A good string replace method would be good in the future :) Anyone have any ideas of how to do this without messing with the kernel? Olav Bringedal Senior Consultant http://Umoe-consulting.no
Łukasz Serwatka	Wednesday 02 February 2005 6:36:50 am Hi, I didn`t test it but should work... {Checking if attribute is not 0} {section show=ne($node.object.data_map.your_attr_name.data_int, 0)} blank {section-else} {attribute_view_gui attribute=$node.object.data_map.your_attr_name} {/section} Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
Olav Bringedal	Thursday 03 February 2005 12:54:16 am there you go... my one track mind looking for solution in the wrong place. So simple, im ashamed i didnt think of that. Thanks a lot for good and quick answer :) Senior Consultant http://Umoe-consulting.no

Author

Message

Olav Bringedal

Wednesday 02 February 2005 6:20:53 am

Heya

I got a class that got 20 fields of integer. In the view template I'd like every value that's not 0 to show as blank.

I tried rewriting the wash method with adding a "notzero" attribute, but that's not a slick solution at all. A good string replace method would be good in the future :)

Anyone have any ideas of how to do this without messing with the kernel?

Olav Bringedal

Senior Consultant
http://Umoe-consulting.no

Łukasz Serwatka

Wednesday 02 February 2005 6:36:50 am

Hi,

I didn`t test it but should work...

{*Checking if attribute is not 0*}
{section show=ne($node.object.data_map.your_attr_name.data_int, 0)}
    *blank*
{section-else}
    {attribute_view_gui attribute=$node.object.data_map.your_attr_name}
{/section}

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

Olav Bringedal

Thursday 03 February 2005 12:54:16 am

there you go...

my one track mind looking for solution in the wrong place. So simple, im ashamed i didnt think of that.

Thanks a lot for good and quick answer :)

Senior Consultant
http://Umoe-consulting.no

eZ debug

Timing:	Jan 31 2025 01:28:13
Script start
Timing:	Jan 31 2025 01:28:13
Module start 'layout'
Timing:	Jan 31 2025 01:28:13
Module start 'content'
Timing:	Jan 31 2025 01:28:13
Module end 'content'
Timing:	Jan 31 2025 01:28:13
Script end

Main resources:

Total runtime	0.0227 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0057	588.1250	151.2109
Module start 'layout'	0.0057	0.0031	739.3359	220.6875
Module start 'content'	0.0088	0.0122	960.0234	997.8047
Module end 'content'	0.0210	0.0017	1,957.8281	33.9922
Script end	0.0227		1,991.8203

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0028	12.4304	14	0.0002
Check MTime	0.0011	4.9839	14	0.0001
Mysql Total
Database connection	0.0013	5.5757	1	0.0013
Mysqli_queries	0.0020	9.0161	3	0.0007
Looping result	0.0000	0.0525	1	0.0000
Template Total	0.0012	5.5	1	0.0012
Template load	0.0010	4.2861	1	0.0010
Template processing	0.0003	1.1437	1	0.0003
Override
Cache load	0.0007	3.1341	1	0.0007
General
dbfile	0.0014	6.1517	8	0.0002
String conversion	0.0000	0.0273	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