Category Archives: Tridion

Running the Tridion deployer in your IDE

Whenever you publish a page, component or another type of item in Tridion, the item is first published, then transported and finally deployed. SDL offers various ways to extend or modify this deployment process. All you need to do is write some custom java code. The most commonly used extension points are deployer modules and storage DAOs. You can find more about this here and here.

In this post I’m not going to explain what these extensions are and what you can do with them. Instead, I will focus on how to develop this type of extension effectively. As always with Java (in my experience at least), the code is easy but the environment is hard. But if you follow these instructions, you will be able to run your customizations locally, make sure they get triggered, and even perform step-through debugging on your code. Pure bliss!

Continue reading

SDL announces extended support for Tridion 2013 SP1 HR1

Earlier this week SDL announced standard support for Tridion 2013 SP1 HR1 is extended until December 2019, with extended support available in 2020.

Hotfix rollup 1 (HR1) for Tridion 2013 SP1 was released by SDL in December 2014. The hotfix rollup includes hotfixes for Content Manager, Content Manager Explorer, Experience Manager, Content Delivery, Translation Manager, and Audience Manager and Outbound E-mail.

Switching to the DXA 2 model service in your DD4T application

On February 12th, SDL released DXA 2.0, the shiny new version of the Digital Experience Accelerator. Part of this new version is a new REST service called the model service, which is able to return content quicker, and in a leaner format. Not only that, the model service is also able to resolve links in the content on the fly. This is an important improvement, because link resolving is one of the most expensive operations in DXA as well as DD4T.

A full migration of your application from DD4T to DXA is far from trivial, at least not with the DXA 2.0 release that is currently out. But there is good news: it is very easy to start using the DXA model service in your DD4T .NET application (it is also possible with a Java DD4T application, but we’ll discuss that some other time). Your application is likely to become faster because of it.

There is one important condition: you have to use SDL Web 8.1 or higher, and DD4T 2.0 or higher, in order to upgrade to the model service.

Continue reading