Continuing on with the creation of Alchemy Plugin videos, I’ve just added a new one to show how to upload a bunch of multimedia items into SDL Tridion. The video is posted after the jump.
In http://www.tridiondeveloper.com/intro-to-the-event-system I described the overall event system, listing many of the options available, but not describing them in detail. One of these options requires further examination: Asynchronous Events.
Asynchronous Events happen outside of the regular process of the code that is running. They may run now, or they may run later. You can think of Asynchronous Events as “Fire And Forget” rockets. Sometimes that’s exactly what you need, and sometimes that’s exactly the wrong thing. Let’s look at some scenarios for both.
When mass publishing content from Tridion, the publish job is handled as a single transaction. Using the Alchemy Page Publisher plugin it’s possible to perform this task but create single items for publishing.
After the jump I’ve created a short video to demonstrate this functionality.
We’ve been quietly releasing some new plugins over at the Alchemy Webstore. As part of those releases I’ve made some quick demonstration videos as it’s far nicer to watch a video showing how to use a plugin than reading the description
To crack things off, after the jump we have the first in the series dedicated to generating Tridion documentation automatically.
With a number of versions of SDL Tridion, SDL Web (and soon to be SDL Tridion Sites) out there with Alchemy users, our latest version of the plugin development framework contains some major updates for the core service.
There’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.
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.
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.