All posts by Quirijn Slings

The template builder is (sort of) portable

The Tridion template builder is a great tool, but it can sometimes be tricky to install. SDL have chosen to distribute it through the ClickOnce mechanism (see https://en.wikipedia.org/wiki/ClickOnce). This does not work with Chrome out of the box, and I haven’t always had good results with the various ClickOnce Chrome extensions out there. Instead, I normally start up IE and point it to the CM site, click on the Tools ribbon and install the Template Builder from there.

There are times when even this approach does not work, for example if I’m working on some locked down machine. For these occasions it is good to know that the Template Builder is portable – or rather portable-ish.

Continue reading

Customizing binary paths in DD4T

SDL Web (formerly called SDL Tridion) has a rather particular way to deal with so-called binary files (images, PDFs, Word documents etc). When published, these files are placed in one folder (typically called ‘images’). To avoid conflicts between different binaries with the same file name, a unique ID is appended to the name of the file. A typical URL of a published binary file would be something like http://mysite.com/images/my-image_tcm3-123.png.

But what if you want to make your own rules for binary paths? And what if you are using the DD4T framework as well? In this post I will explain how to customize the paths to your binaries in DD4T.

Continue reading

Using SDL’s microservices in a web farm

SDL Web 8 has been around for a little over a year now. Its successor (SDL Web 8.5) was recently introduced. You’d think that to an old Tridion hand like me, by now Web 8.x would be as familiar as any of the earlier (Tridion) versions. The sobering fact is that today I ran into an issue caused by a poor understanding on my side of SDL’s new microservices architecture. Fortunately it proved easy to fix.

Continue reading

A new approach for serving images from a broker database

A picture says more than a thousand words, right? That’s why a web site needs images. In the old days before DD4T, the approach was very simple: out of the box, Tridion would publish your images to the file system, where the web server could pick them up and serve them out to the world.

But in the era of dynamic publishing, who wants to deploy to a file system anymore? One of the advantages of DD4T (or DXA, or any other dynamic framework) is that you publish everything to one central delivery store: the broker database. It makes sense to use this approach for images (and other binary file types) as well. But how?

Continue reading