Skip to main content

Escaping DWT ${ } Syntax

A while back, I was writing about the Dreamweaver Double Lookup technique for Tridion templating.

I was however struggling with escaping the DWT notation, notably with JSTL Expression Language syntax. The EL syntax is the same with DWT's for outputting variables and expressions: ${ expression }

I used to output EL expressions as $[ expression ] and then have a TBB to replace the square brackets with curly braces.

Finally, I found out today not one, but two ways to escape the DWT syntax ${}. Both following expressions output ${'Hello, world'}
  • ${'$'}{'Hello, world'}
  • @@'$'@@{'Hello, world'}
The trick in both cases is to escape the output of the dollar symbol ($) by using it as String parameter in the surrounding @@ @@ or ${ }. What follows is the normal unescaped {'Hello, world'} output.

Now you know... :)

But, wait... we are not there yet! This approach above, only works from a Dynamic CT or a Page Template. The embedded CT will not work as expected. The reason is the two DWT TBBs that get executed with embedded CPs: one for the CT itself and the second for the PT that outputs the Component Presentation.

An embedded CT that contains the code ${'$'}{'Hello, world'} produces DWT output ${'Hello, world'} and when the PT executes, it generates the final output  Hello, world

So the solution is to encode the string twice (you're heading now for a headache) :)

The embedded CT DWT: ${'$'}{'${'$'}'}{'Hello, world'} - I'll explain below
The CT output (i.e. input for PT): ${'$'}{'Hello, world'} - expression explained above
The PT output: ${'Hello, world'} - the desired JSTL EL output

A similar notation for the CT is: @@'$'@@{'@@'$'@@'}{'Hello, world'}

The way this works:
  • ${'$'} or @@'$'@@ outputs a dollar sign ($);
  • {' outputs normally a open curly brace and an apostrophe;
  • ${'$'} or @@'$'@@ outputs a dollar sign ($) again;
  • '} outputs normally an apostrophe and a close curly brace;
  • {'Hello, world'} outputs normally as-is;


Comments

Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as...

REL Standard Tag Library

The RSTL is a library of REL tags providing standard functionality such as iterating collections, conditionals, imports, assignments, XML XSLT transformations, formatting dates, etc. RSTL distributable is available on my Google Code page under  REL Standard Tag Library . Always use the latest JAR . This post describes each RSTL tag in the library explaining its functionality, attributes and providing examples. For understanding the way expressions are evaluated, please read my post about the  Expression Language used by REL Standard Tag Library . <c:choose> / <c:when> / <c:otherwise> Syntax:     <c:choose>         <c:when test="expr1">             Do something         </c:when>         <c:when test="expr2">             Do something else         </c:when...

Publish Binaries to Mapped Structure Groups

Today's TBB of the Week comes from the high demand in the field to publish binary assets to different mapped Structure Groups. By default SDL Tridion offers two ways of publishing binaries: All binaries publish to a folder defined in your Publication properties; All binaries rendered by a given template publish to a folder corresponding to a given Structure Group; In my view, both cases are terrible, over-simplified and not representing a real use-case. Nobody in the field wants all binaries in one folder and nobody separates binary locations by template. Instead, everybody wants a mapping mechanism that takes a binary and publishes it to a given folder, defined by a Structure Group, and this mapping is done using some kind of metadata. More often than not, the metadata is the TCM Folder location of the Multimedia Component. I have seen this implemented numerous times. So the solution to publish binaries to a given location implies finding a mapping from a TCM Folder to a...