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

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven