Welcome to the first blog post of 2021! (funny enough also my first blog post)
Recently while trying to work on a direct integration between a React Single Page Application and the GraphQL endpoint of the microservice, I encountered the following errors in the React application:
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.
It is a common practice of almost everybody who works with Tridion: copying text from Word or Excel into a rich text field in Tridion. Unfortunately, when you do this you end up copying much more than just the text. Styling characteristics also find their way into the rich text field, in the form a style attributes, class attributes, comments, unnecessary spans, and even complete sets of CSS classes. And when a component with such a rich text field is published, all this styling finds its way to your site, where it is very likely to clash with your carefully designed pages.
Of course, you can circumnavigate this issue by copying first to a text editor like Notepad, copy it again and then pasting it into Tridion. But there is a more elegant solution for this problem. It requires just a tiny bit of work.
Today SDL announced the release of SDL Tridion Sites 9.5, the successor of SDL Tridion Sites 9.1. The new release includes the long-awaited new UI called Experience Space consisting of various improvements for content editing. An overview of new features and functionality is included in the documentation available from SDL’s Documentation Center.
When you publish an item in Tridion, all items linking to this item are also published, on 2 conditions:
– The linking item is already published
– The checkbox ‘If other published Components link to a Component you are publishing, publish or republish those Components’ is checked (this is the default)
I don’t know if this principle has an official name, but I call it ‘reverse link propagation’, because it follows links backwards and propagates the publishing action to the linking items.