Tridion (or SDL Web as it’s called nowadays) allows many extension points. You can extend the content editor GUI, you can extend events, and you can also extend a lot of things on the content delivery side, for example Ambient data claimprocessors, TCDL tag handlers, storage extensions, …
These content delivery extension points are usually written in Java.
This blog post will show you how you can easily add your own configuration files for your code.
Tridion 2013 provides us with a number of powershell commands for some tasks like purging different Tridion queues, or reindexing the internal Tridion search index.
“Tridion seems to choose random times to not check in my items and I don’t notice it until I’m well into my debugging.” I’m sure I’m not the only one who has heard this, or thought it silently to myself. Of course, everyone knows that software doesn’t often do “random”, and if you pay enough attention and get a little lucky you can usually find a pattern to when an unexpected behaviour is happening. In this case I’ve spoken to a number of experienced Tridion users and gotten some good ideas on why items might stay open.
Recently I’ve been working with a client that has fairly heavy publishing requirements. The blueprint contains over 300 publications, each containing a couple hundred pages. This means a release with widespread impacts can easily lead to 10-20 thousand published items. Luckily, we’ve scaled out publishing to the point where this ordinarily isn’t a problem. However, we were still noticing intermittent problems with our deployer. These came up in two main ways:
- Publishing getting stuck in a “throttled state”, even when all other tasks in the queue were either successfully published or waiting for publish
- The publishing queue showing all publishes stuck on a “ready for transfer state”, even though the files on the file system were being updated
One of the features of Alchemy that I think will end up being the most helpful in the future is the way it lets you build a plugin and never have to worry about whether it’ll stop working with future versions of Tridion. This is because Alchemy provides helpful wrappers for the Anguilla framework used to interact with the CMS. If Tridion ever moves on from Anguilla (as has long been rumoured) Alchemy will update the wrappers to support the new technology and if your plugin is using these wrappers you shouldn’t even have to think about it. Continue reading
Recently one of my coworkers was saying she didn’t know who Hall & Oates were. This got me thinking, what better way to preserve the legacy of the great rock and soul duo than adding John Oates’ moustache to some Tridion icons. So, for anyone interested in Oatesifying your CME, follow these steps.
- Download the image at the end of this post
- Go to %TRIDION_HOME%\web\WebUI\Editors\CME\Themes\Carbon2\Sprites
- Rename cme_Sprites.32px.png to cme_Sprites.32px_old.png
- Copy the downloaded image to this location
- Open %TRIDION_HOME%\web\WebUI\WebRoot\Configuration\System.config
- Increment the modification attribute of the server version
- Clear your cache and reload Tridion
- Enjoy the Oates!
Hoping this blog will help you guys if you receive the same error I encountered today whilst configuring the Tridion 2013 SP1 deployer as a .Net application.