A note for those who need to escape the character "{" in templates

Next topic

Author	Message
Volker Lenz	Thursday 30 January 2003 9:44:20 am If you are using javascript functions or inline style-declarations in your page layout templates, you will have faced the problem of how to escape the character "{", so that the ezp template parser won't destroy e.g. the opening brackets of your javascript functions. The recommended way to accomplish this is to use the "{literal}" and "{/literal}" operators. However, these operators are buggy in ezp3-rc1. Another way that does the job without using "{literal}" is using "{ldelim}" and "{rdelim}" where you want to get "{" and "}" in your template output. "{ldelim}" and "{rdelim}" are internal functions of the ezp template parser. These functions let the parser print out just the parser-tags it uses. There is one little caveat to keep in mind when you use the "{ldelim}" and "{rdelim}": If the ezp-devs should actually decide to use another standard tag instead of "{" and "}" for their template parser, you will have to change your own templates, too, since "{ldelim}" and "{rdelim}" will always print out the parser tag in use, and if this tag should be changed to say "{#", your javascript-functions will also get an "{#" as opening bracket. However, this seems not to be a serious danger for template designers, since most of you are probably using an editor tool capable of replacing text chunks as needed. So if some day the "{ldelim}" and "{rdelim}" are no longer appropriate, we may easily change them to whatever may be appropriate then.
Jan Borsodi	Friday 31 January 2003 12:49:25 am > If you are using javascript functions or inline > style-declarations in your page layout templates, you will > have faced the problem of how to escape the character "{", > so that the ezp template parser won't destroy e.g. the > opening brackets of your javascript functions. > The recommended way to accomplish this is to use the > "{literal}" and "{/literal}" operators. However, these > operators are buggy in ezp3-rc1. > > Another way that does the job without using "{literal}" is > using "{ldelim}" and "{rdelim}" where you want to get "{" > and "}" in your template output. "{ldelim}" and "{rdelim}" > are internal functions of the ezp template parser. These > functions let the parser print out just the parser-tags it > uses. > > There is one little caveat to keep in mind when you use the > "{ldelim}" and "{rdelim}": If the ezp-devs should actually > decide to use another standard tag instead of "{" and "}" > for their template parser, you will have to change your own > templates, too, since "{ldelim}" and "{rdelim}" will always > print out the parser tag in use, and if this tag should be > changed to say "{#", your javascript-functions will also get > an "{#" as opening bracket. > > However, this seems not to be a serious danger for template > designers, since most of you are probably using an editor > tool capable of replacing text chunks as needed. So if some > day the "{ldelim}" and "{rdelim}" are no longer appropriate, > we may easily change them to whatever may be appropriate > then. The preffered method for getting { in the template is to use the {literal} tag, it will work when RC2 gets out the door (which should be quite soon). Using {ldelim} and {rdelim} will work too since we have no intention of changing them into other delimiter characters, the reason for having them configurable is when eztemplate is used outside of eZ publish and one is interested in having other delimiter characters. The third option to getting javascript in template is to place them in separate .js files and use HTML tags to include them. -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq
Jeroen van Gorkum	Tuesday 04 February 2003 8:09:45 am > The third option to getting javascript in template is to > place them in separate .js files and use HTML tags to > include them. ...which is the preferred method in xhtml anyway, to work around problems with '<!--', '-->', '<' and '&' in the page itself. (see Script and Style elements: http://www.w3.org/TR/xhtml1/#h-4.8, and http://doxdesk.com/personal/posts/wd/20010911-cdata.html.)

Author

Message

Thursday 30 January 2003 9:44:20 am

If you are using javascript functions or inline style-declarations in your page layout templates, you will have faced the problem of how to escape the character "{", so that the ezp template parser won't destroy e.g. the opening brackets of your javascript functions.
The recommended way to accomplish this is to use the "{literal}" and "{/literal}" operators. However, these operators are buggy in ezp3-rc1.

Another way that does the job without using "{literal}" is using "{ldelim}" and "{rdelim}" where you want to get "{" and "}" in your template output. "{ldelim}" and "{rdelim}" are internal functions of the ezp template parser. These functions let the parser print out just the parser-tags it uses.

There is one little caveat to keep in mind when you use the "{ldelim}" and "{rdelim}": If the ezp-devs should actually decide to use another standard tag instead of "{" and "}" for their template parser, you will have to change your own templates, too, since "{ldelim}" and "{rdelim}" will always print out the parser tag in use, and if this tag should be changed to say "{#", your javascript-functions will also get an "{#" as opening bracket.

However, this seems not to be a serious danger for template designers, since most of you are probably using an editor tool capable of replacing text chunks as needed. So if some day the "{ldelim}" and "{rdelim}" are no longer appropriate, we may easily change them to whatever may be appropriate then.

Jan Borsodi

Friday 31 January 2003 12:49:25 am

> If you are using javascript functions or inline
> style-declarations in your page layout templates, you will
> have faced the problem of how to escape the character "{",
> so that the ezp template parser won't destroy e.g. the
> opening brackets of your javascript functions.
> The recommended way to accomplish this is to use the
> "{literal}" and "{/literal}" operators. However, these
> operators are buggy in ezp3-rc1.
>
> Another way that does the job without using "{literal}" is
> using "{ldelim}" and "{rdelim}" where you want to get "{"
> and "}" in your template output. "{ldelim}" and "{rdelim}"
> are internal functions of the ezp template parser. These
> functions let the parser print out just the parser-tags it
> uses.
>
> There is one little caveat to keep in mind when you use the
> "{ldelim}" and "{rdelim}": If the ezp-devs should actually
> decide to use another standard tag instead of "{" and "}"
> for their template parser, you will have to change your own
> templates, too, since "{ldelim}" and "{rdelim}" will always
> print out the parser tag in use, and if this tag should be
> changed to say "{#", your javascript-functions will also get
> an "{#" as opening bracket.
>
> However, this seems not to be a serious danger for template
> designers, since most of you are probably using an editor
> tool capable of replacing text chunks as needed. So if some
> day the "{ldelim}" and "{rdelim}" are no longer appropriate,
> we may easily change them to whatever may be appropriate
> then.

The preffered method for getting { in the template is to use the {literal} tag, it will work when RC2 gets out the door (which should be quite soon).
Using {ldelim} and {rdelim} will work too since we have no intention of changing them into other delimiter characters, the reason for having them configurable is when eztemplate is used outside of eZ publish and one is interested in having other delimiter characters.

The third option to getting javascript in template is to place them in separate .js files and use HTML tags to include them.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

Jeroen van Gorkum

Tuesday 04 February 2003 8:09:45 am

> The third option to getting javascript in template is to
> place them in separate .js files and use HTML tags to
> include them.

...which is the preferred method in xhtml anyway, to work around problems with '', '<' and '&' in the page itself. (see Script and Style elements: http://www.w3.org/TR/xhtml1/#h-4.8, and http://doxdesk.com/personal/posts/wd/20010911-cdata.html.)

eZ debug

Timing:	Jan 18 2025 05:21:21
Script start
Timing:	Jan 18 2025 05:21:21
Module start 'layout'
Timing:	Jan 18 2025 05:21:21
Module start 'content'
Timing:	Jan 18 2025 05:21:22
Module end 'content'
Timing:	Jan 18 2025 05:21:22
Script end

Main resources:

Total runtime	0.9290 sec
Peak memory usage	4,096.0000 KB
Database Queries	59

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0060	588.3984	152.6875
Module start 'layout'	0.0060	0.0044	741.0859	39.5234
Module start 'content'	0.0103	0.9171	780.6094	588.7188
Module end 'content'	0.9274	0.0015	1,369.3281	16.0781
Script end	0.9290		1,385.4063

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.3544	16	0.0002
Check MTime	0.0013	0.1423	16	0.0001
Mysql Total
Database connection	0.0009	0.0931	1	0.0009
Mysqli_queries	0.8686	93.4973	59	0.0147
Looping result	0.0007	0.0741	57	0.0000
Template Total	0.8930	96.1	2	0.4465
Template load	0.0021	0.2288	2	0.0011
Template processing	0.8908	95.8910	2	0.4454
Template load and register function	0.0001	0.0129	1	0.0001
states
state_id_array	0.0008	0.0861	1	0.0008
state_identifier_array	0.0016	0.1691	2	0.0008
Override
Cache load	0.0019	0.2002	50	0.0000
Sytem overhead
Fetch class attribute can translate value	0.0010	0.1078	3	0.0003
Fetch class attribute name	0.0014	0.1504	5	0.0003
XML
Image XML parsing	0.0013	0.1419	3	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0011	5	0.0000
General
dbfile	0.0010	0.1061	23	0.0000
String conversion	0.0000	0.0053	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
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
4	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
4	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 15 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs