Extending the SDL Knowledge Center GUI

Many of us are familiar with GUI extensions in SDL Web, as well as Alchemy plugins, which integrate into the GUI via the Aguilla JavaScript framework. With SDL Knowledge Center, the story is a bit different. At first glance, Knowledge Center appears to have a GUI very similar to Web’s, in terms of look and feel. Under the hood, however, it’s implemented differently. There is no Anguilla. Anguilla is more of a Tridion thing. And from my experience, the concept of a GUI extension does not really exist in KC. There is documentation on plugins and extensions. But there is no clear, simple approach to extending the GUI, as far as I can tell. In this post, I outline a simple technique for extending the GUI functionality of your Knowledge Center implementation.

Continue reading

Finding duplicate binaries in your SDL Tridion Publication

duplicate filesThere’s been quite a lot written about Duplicate Binary Issues in SDL Tridion.  A couple of years ago I released a PowerTool to solve this issue.    Knowing it can still be troublesome for some SDL Tridion users, I decided to give it a little rewrite and release it as an alchemy plugin.

Continue reading

SI4T-Solr 1.2 for Web 8

Looking at code you wrote three years ago can sometimes be a confronting experience. In case of the code I wrote for SI4T, this was no different. After you go through the six stages of debugging and cringe at the aestestics of the code base, the only thing you can do is rewrite the stuff with the knowledge of today and be solaced by the fact that your code is actually used in production environments and not breaking too much.

Continue reading

Web 8, SI4T and Storage Extensions

The release of SDL Web 8 has seen the biggest overhaul of the Content Delivery stack since Tridion 2011 and much of it has been applauded much, as the new Micro Services architecture and with it the ability to scale, deploy and be distributed in general, gives many more architectural options than just having an API in your web application connecting you to a database.

Building this while guaranteeing backward compatibility with the Tridion 2011/2013 CD stack is more than a major task and I for one am happy to see that that feat was pulled off really well. That is, unless you have overridden the default DAOFactory classes in your Deployer Storage Extensions, as is the case with the SI4T Storage Extensions. When testing SI4T with Web 8, it turned out that loading of the SI4T Storage Extension did not work in every scenario. This has to do with the subtler points of Spring Bean Class loading.

Continue reading