Documentation Center

Publish undo constraints

Under certain circumstances, publish undo functionality does not work in combination with a Content Delivery setup that publishes to file system.

Custom items in Transport Package

If your implementation of SDL Tridion adds custom items to the Transport Package, rendering instructions related to such content (if related to Pages or Component Presentations) is stored as a general content type 'extension data'.

If you intend to make it possible to undo the publishing of such data, then you must have database storage set up for your normal publishing, rather than file system storage. Otherwise, publish undo will not function properly.

Non-default character set encoding

If you publish to file system, Content Delivery does not store the character set used to encode the page content. Instead, it is assumed that the content is encoded in the default character set of the operating system on the machine where the content was published.

This assumption must be true for undo to work properly. In other words, in order for undo to work when publishing to file system, you must encode the content you publish using the default character set on the machine where the published content will be stored.