It can be very useful to set the log level of Tridion’s content service to Debug every once in a while. I admit I always do that on my own development environments – you never know when you will need it. Of course, I would not recommend it for production environments but that’s another story.
One thing is really annoying though: every 10 seconds, the content service makes a call to the discovery service (for whatever reason, perhaps to check the validadity of the tokens or something). And this leads to so much logging that you always have to wade through endless lines of useless logging before you get to the interesting bits.
Today, version 2.6 of DD4T.Model was released. It contains bug fixes and security patches. Most important changes:
- Fixed a bug with the serialization of keywords, reported on Stackexchange (https://tridion.stackexchange.com/questions/21828/upgrade-to-tridion-9-5-and-net-dd4t-2-5-producing-error-with-ikeyword-on-dynami)
- Upgraded Newtonsoft.JSON to 13.0.1 (with improved security)
When setting up a new Tridion environment for a client or for testing purposes, there is often a requirement for a quick sample web application. To verify all connections and configuration are set up correctly, or sometimes just to hit some URLs and see some information on the page. This can be useful for instance when dealing with a copied database or in the process of a Tridion upgrade to the latest version. This blog post will demonstrate the quickest and easiest way to get the basics up and running.
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.