It should never happen, but somehow it occasionally does: duplicate records in your broker database. For example: if you have a deployer for staging and another one for live, but you accidentally point them to the same broker database. When this happens, you might end up with 2 (or more) pages in the broker, with the same publication ID and the same URL.
Do you want to know if this is the case for you? Read on.
The Tridion publish queue, what can I say about it that wouldn’t be censored by the authorities right away? It can be horribly slow, that’s for sure. This is mainly because so much data is going across the line.
If you have access to the Tridion CM database, you can save yourself valuable time, but the results are sometimes hard to understand. Here is a trick to improve that!
In SDL Tridion Sites 9.1, which was released last week, the page region functionality has received a small update. Besides a few bugfixes, the main enhancement is in the so-called synchronization of pages.
A while ago I blogged about running your custom deployer logic in a Java IDE. That article was based on my experiences with SDL Web 8.5 (aka Tridion 8.5) and the *.bat file and pom.xml that were given in that article were based on this version.
Total, I’m here to tell you that the same thing is possible in Tridion 9.
The process of creating components in Tridion has always been very different from creating pages. When you create a component you are guided by a schema, which provides strict guidelines. However, when you want to create a page, you start off with a tabula rasa – essentially a blank sheet of paper.
This changes with the introduction of regions and page schemas. Here’s how. Continue reading