Skip to main content

Referencing Image Variants from Dreamweaver Templates

OK, so you've written your Resize Image TBB that publishes a variant image... But now you need a reference (e.g. the URL) of this variant in DWT. How would I get that?

The first thing I tried, in my DW TBB, was to reference the image variant using the attribute tridion:variantId. How cool it would be that by just referencing the image TcmUri and variantId in DWT to actually have that resolved and replaced by the Resolve Links default TBB. Something like this:

<img src="tcm:1-2" tridion:variantId="thumbnail"/>

Well, it doesn't work! The TBB Resolve Links doesn't know about attribute tridion:variantId on an img element.

So, I told myself "I will write My Own Resolve Links TBB" and I started investigating... What I tried was retrieving the image variant from the package (lookup by name or Tcmuri), then identify the one I needed by matching on the variantId. Well, that doesn't work either! It seems that there is only one MMComponent in the Package, added by the DW TBB and that one does not have a variantId (i.e. this is the original MMComponent). I event iterated over the entire Package hoping to identify the image variant added by RenderedItem.AddBinary() method. It is not in the package! So I could not retrieve it!

Next, I tried adding the image variant to the package and specify the variant myself. I quickly abandoned this approach, simply because I could not find a Package.Create*Item that would allow me to add a MMComponent with a variant. Seemed like a dead-end!

Finally, I still had to solve this problem, so I ended up using the good old method of creating a String package item holding the URL of the image variant. The following code goes at the end of the Resize Image TBB.

Binary binary = m_Engine.PublishingContext.RenderedItem.AddBinary(
    resizedStream, newFilename, variantId, mmc,

    m_Package.CreateStringItem(ContentType.Text, binary.Url));

Therefore in DW TBB, you would just use @@MyImage@@ to output the image variant URL.

<img src="@@MyImage@@"/>


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: I stumbled upon the following post from 2008 (!!!), , 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