How Do I Revert Back to a Previous SDL Tridion Item's Version?

Sometimes you want to go back to a previous version of an item (page or component) in SDL Tridion. Here are the steps for your content editors.

From a publication an item is local to (localized or in a parent publication), an authorized author (with read/write/delete permissions) can do the following:

Right-click > Versioning > History

Recognizable SDL Tridionauts: An Answerer, a Coder, a Community Builder, Mr P, and the Button Presser.

SDL itself has a few visible Tridionauts in the community. You might recognize them by their online behavior below.

KnewKnow

If someone concisely answers your Tridion question regardless of the channel (Linked-In, StackOverflow, or scribbled on a wall in a customer's war room), it might be Nuno Linhares. He will answer questions wherever he finds them.

KnewKnow thinks, "Ooh, a Tridion question."

Q? A.

Mr. Code-ariu

If you follow a link in someone's answer and find a Tridion code snippet as a reference, it might come from Mihai Cădariu. He will share interesting pieces of code that most often he writes himself.

Mr. Code-ariu thinks, "Ooh, Tridion code."

0100001101101111011001000110010100100001

Dynamic Vs. Static Component Presentations Vs...

I recently made the mistake of asking a client about their preference for dynamic versus static component presentations and of course got the response, "we prefer dynamic!"

Component presentations (CPs) are simply the combination of some content (a component in Tridion) and how it displays (with a template in Tridion). When created by an author, these CPs on a page display according to page template rules. CPs on a Page are a Good Thing. They are appropriate with context, placement, and order matters. CP behavior is configured in your Component Templates.

Nothing Wrong with CPs on a Page

I prefer terms such as "embedded," "curated," or "assembled" to refer to Component Presentations on a Tridion Page. "Static" works, but as seen in my story, it suggests there's something outdated or wrong about assembling pages. There's nothing wrong with a Tridion page with embedded Component Presentations!

Fun with SDL Tridion Icons and Visio Stencils

You might notice the SDL Tridion Carbon theme icons in my posts. I use them often enough in my explanations that I added a stencil in Visio 2010 (under the Shapes dialogue click on More Shapes > New Stencil).

This lets me quickly add pictures, diagrams, and text to Visio designs by clicking and dragging them onto Visio's drawing area. For example I created the following building block summary and "refreshed" some existing diagrams.

Building Blocks

Not a perfect breakdown, but I grouped the Tridion Building Blocks (items) along two axis: purpose at the top and what they're mostly/sort of related to along the left. If I add some stats and arrows it'd make a nice info graphic.

Applying CMS Principles To Your CMS Designs

Do you promote best practices in your SDL Tridion implementation? Are these important to your content management perspective?

• Do you separate content from layout?
• Should design changes be consistent and easy to manage?
• Do you prefer to make future update easy?

If you answered yes, let's apply these to your functional and technical designs by placing text with the boxes or graphics they describe, creating documents that are easy to update, and using the right tools.

Experience Manager Content Types and Regions

I've seen and had questions about the relationship between SDL Tridion Pages, Regions, and Content Types with Experience Manager (XPM), the inline editing interface.

• User Harald Hoffelinck had the same question on StackOverflow. 
• I asked how to confirm how to control what gets added to a page as well.

The concepts can easily get blurry, considering the definitions: