You may have heard the buzz about a new major release of the most popular content delivery framework for Tridion? Well, get ready: the ever-growing community is about to release DD4T 2.0. In fact, a beta-release of the DD4T 2.0 Templates was released to the public a couple of days ago.
Yearly Archives: 2015
Catching items that come back from translation
If you are reading this, you probably know that Tridion has an event system which allows you to attach your own custom functionality to pretty much everything that goes down. A typical example is to perform some pre-processing of an item before it is saved.
The customer I work for at the moment had just such a requirement. The only thing was: the pre-processing should only occur if the item in question was updated by SDL’s translation management system. The question is: how can one see that a ‘save’ action was triggered by TMS, and not by a regular user or some other system activity?
Event system deploy script
Developing event system modules is all in a day’s work for a Tridion professional. Deploying your modules is simple enough, but can get quite tedious. You need to shut down services, stop IIS, copy some DLLs to the Tridion bin folder, install other DLLs in the GAC, start IIS, restart services…
Today I got fed up so I wrote a windows batch script that automates all that. It isn’t earth-shattering, just a little thing that might help save you a few minutes of your precious time.
It works ONLY with Tridion 2013 by the way. On 2011 and before, you need to shutdown the COM+ as well, and that is not so easy to do.
Here is how to build a package for your event system, and deploy it with the script.