How to delete a publication from Tridion
Recently I came across a post (and a fellow Tridion blogger, keep up the good work!) which answered the question “Why won’t this publication delete?“. It describes a tool (source code included) which helps you find the pages which you need to unpublish before you can delete the publication. It mentions two prerequisites which need to be met before you can delete a publication:
- No pages in the publication are published
- There are dependencies on the publication, child publications etc.
I would like to add a third prerequisite:
- Check the publishing queue for publish transactions which belong to the publication to be deleted which have the status “in progress”. In some instances publication transactions never leave this state and they will prevent you from deleting the publication.
In addition I would like to propose another way of ‘unpublishing’ all items in a publication (pages, components, MM components etc) by running the following query on the CM database (back-up the DB first) :
Read more
Howto publish folders from SDL Tridion
In the Tridion cms content is being stored in folders. The folders are similar to folders in file systems, they contain both subfolders and components. However if you wish to publish the content of an entire folder you will have to traverse all subfolders yourself in order to select and publish the components manually. Not exactly a job for volunteers.
Fortunately there is something called the Tridion API which allows you to write a (power)tool which takes care of traversing a folder hierarchy and republishing all the content in it. This will reduce the effort of republishing an entire folder to an acceptable level and give any script kid a huge sense of accomplishment.
Alas a tool like this is not very friendly to the users of the Tridion cms. They will ask why it is impossible to publish a folder in the same manner they can publish a structure group. The answer to this question is unknown to me at this point in time. Perhaps one of the Tridion employees reading this blog can enlighten me on this subject (and approve my comments on ideas.sdltridion.com). Read more
Publish XML or HTML from Tridion?
I created a small evaluation in order to make a substantiated choice between publishing XML or HTML from Tridion. I already assume that you made the choice between static and dynamic publishing Perhaps it will be of interest to someone:
| XML | HTML | |
|---|---|---|
| Separating content and presentation / Re-usability of data. Since the web application completely determines how or which parts of the XML content is presented, the same content can easily be displayed in different ways. |
+ | - |
| Tridion publishing Performance. When publishing XML content, Tridion only needs to render one Component Presentation which will take less time then rendering multiple Component Presentations. |
+ | - |
| Maintenance and extension of Component Templates. Your templates in Tridion will be simpler and thus easier to maintain. The complexity is transferred to the web application which is much easier to main then Tridion templates (try debugging or refactoring your code in Tridion). |
+ | - |
| Minimizing CMS development dependencies Changes in the HTML templates will not result into changes of the CMS template code. |
+ | - |
| Presentation performance. Rendering the XML into HTML on the presentation server will use more resources then displaying plain HTML. |
- | + |
| Complexity of the web application The web application will be partially responsible for rendering the content. |
- | + |
| Grand total | + | - |
About Albert te Boekhorst
This is the professional blog of Albert te Boekhorst. Albert is a manager in the Web Solutions service line at Deloitte Consulting.
Posts from colleagues
Powered by FireStats