Recently a client required a way of creating and storing ‘dynamic’ values within the content managed in SDL Tridion. Â By ‘dynamic’, this could be anything from loan rates, petrol prices or the cost of a pint of beer. Â So today ‘pint_beer_cost’ could be $3.50, tomorrow it could be $4.50. Â Having to go through all stored content and replace $3.50 with $4.50, every time there is a need to change a value would be quite painful.
Who doesn’t love PHP? PHP is used by over 20 million web sites and 1 million servers so chances are you may need to build a website in SDL Tridion that is publishing out PHP files to your web server.
One of the things that developers new to the SDL Tridion templating language struggle with is the creation of web-page layouts that are built up using rows and columns of content. I hope this short post shows a simple way to built this logic into your SDL Tridion layouts.
If you’re following the SDL Tridion guidelines for implementing the new UI within your compound page templates (Link – Note log-in required) you’ll notice that you need to specify the URL of your CME enviroment. As this value is required on each page template that will utilize UI functionality, this could be a bit of a pain to manage once you migrate your templates between different environments (Development, QA, Production etc). It doesn’t need to be, here is a simple solution to make content porting and migration easier to work with.
If you’re looking to generate a sitemap.xml file, this post contains a handy TBB to use as a starting point for your development.
For anyone that would like the slides from today’s SDL Tridion community webinar here are the downloads:
Thanks Jules/SDL for having us and we’re looking forward to the next one.
Just wanted to post up a quick code snippet showing how to get a list of used items XML using the SDL Tridion 2011 core service. Why? Well previously the API typically used to work like itemType.GetListUsedItems() (where itemType is a Component or Page object etc), where as now the ‘Using’ and ‘Used’ items are read using a filter via the core service client method .GetListXML().
HTML published from Tridion is typically created using Tridion Dreamweaver Templates (DWTs). These templates can involve a lot of ‘If’ statements to check that values exist or what their value is etc. I like to put line breaks between each DWT statement so that its easier to read and work with, which usually looks something like this (actually it can get a lot crazier than this!):
This post is part 3 of 3 that explains how to install the Image Map extension for SDL Tridion. Please also read the image map extension introduction and details about how to use it.
Note: This will only work on SDL Tridion 2011, that said it would be really easy to get this working on 2009, contact me if you’d like some help with it.
The Image Map tool is built using HTML and Javascript (Not my javascript, the excellent javascript of these guys), it plugs directly into multimedia components as a custom field in the multimedia schema.
Now you’ve got the Image Map extension installed, you’re now to ready to dive in and create loads of image maps 