So, you’ve got a release going on and some 20 people are publishing. A few of the editors only have a page or two to publish but some of them then select to publish the whole site and a few have published only whole Structure Groups!
How many of these publish by Structure Group! And, I ask, Why?
Why do it in the first place?
The first answer I hear a lot is
I don’t know exactly what to publish
Recently I have had the pleasure of debugging XPM issues, which is high on a Tridion developer’s list of favourite pass times. I got a special bonus though, because in addition to the common, and often discussed session preview errors, I had a seemingly unique error killing XPM in Firefox and Internet Explorer before it could load:
I recently worked with a small team within Content Bloom to migrate over 200 gigabytes of binary files into SDL Web. Actually it was 244 Gigs to be exact ☺
It was quite a learning experience and I wanted to share some of that learning.
I recently implemented an Audience Manager integration in a Web 8 DD4T (.NET) project. I was scratching my head for a long time about an error message that didn’t seem to make sense:
Unable to determine the current Publication. Please make sure the Ambient Data Framework is running, or configure a DefaultPublicationId in the cd_audience_manager_conf.xml configuration file
Recently I was involved in the setup of a new content-delivery environment, migrating from a WebSphere 7.* application server to WebSphere 8.5.5. Right away when we started up the application, we started seeing some content-delivery errors with our session preview web-service which we did not experience on WebSphere 7. I’m going to review the problem, and talk about how it was resolved. Continue reading
Reading the docs, you would be led to believe that creating Fredhopper triggers was a matter of editing the trigger-types.xml file. It is however also possible to do this programatically – a trick that can come in handy should you not have access to that file on Production, or you wish to manage your triggers through automation.
When most people think of SDL Tridion/Web 8 they think of a kick-ass content management system to run their website. And they’re right! But, the thing about Web 8 is that you aren’t constrained to just providing content to websites. Content is needed on any number of devices these days, from native mobile apps to video game systems to billboards to fancy appliances. Continue reading
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.