Sitecore less known gems - Live site setup

-

Case

A web editor has created a large amount of content that is ready to be published. However, in order to get the final 'OK' on this newly created content, he needs to get the buy-in of specific persons in the company.

The default answer here would be to use the Sitecore preview mode or use well devised workflows within sitecore that are automatically notifying the correct group of persons by sending mails or updating their RSS coupling (in outlook for example). These notifications would in turn push the stakeholder into taking the right actions needed to ensure the content gets published in the correct form.

However, 
what is the best possible approach if your target audience has no knowlegde whatsoever of Sitecore? Users that don't have an account and can not (or should not) be motivated into adopting your well designed Sitecore content approval approach ?

At that point the Sitecore Live Mode can come into play and offer a relatively elegant solution.

What is Sitecore Live Mode ?

When you put a Sitecore website into Live Mode you are basically changing the way Sitecore works with regards to publishing by removing the need for publishing entirely.
Sitecore basically works by using 3 databases: Core, Master, Web.

Wheras the Core database is the beating heart of the CMS and it's users and functionalities, the Master and Web databases hold all the content, languages, versions and so on. And where the Master database holds the full set of content, the Web database holds only the latest (published) version of content.

The Sitecore Live Mode configures the Sitecore website to work solely on the Master database instead of using the published Web database.

When should/can you use Sitecore Live Mode ?

The case described above already gives a good example of when this approach would prove it's value. But I'll try to list some of the cases below:
  • During development; if content needs to be checked, publishing is often needed to check if all Sitecore Items are properly rendered in the front-end. However, live-mode can remove this evil.
  • Having content previewed without the need for people to actually log into sitecore.
  • Making your content management server available for internal purposes such as content validation.

By creating an additional website configuration in the site settings you can provide a URL for internal previewing of content. So, where your public website is made available through http://www.somecompany.com you can have http://preview.somecompany.com be your internally available preview url.

Okay, how do I get this show on the road !?

Setup is actually pretty straight forward. Changes are made to the SiteDefinition.config file by adding a new <site> node. This new node has only a small, but important, number of changes :
  • Load content from the master database: database="master"
  • Set a hostName to bind to: hostName="preview.mysite.com" (DNS and IIS setup needed as well obviously)
  • Don’t filter items which preserves some basic item restrictions: filterItems="false"
  • Enable workflow: enableWorkflow="true"

<site name="website_preview" filterItems="false" enableWorkflow="true" hostName="preview.mysite.com" virtualFolder="/" physicalFolder="/" rootPath="/sitecore/content" startItem="/home" database="master" domain="extranet" allowDebug="true" cacheHtml="true" htmlCacheSize="10MB" registryCacheSize="0" viewStateCacheSize="0" xslCacheSize="5MB" filteredItemsCacheSize="2MB" enablePreview="true" enableWebEdit="true" enableDebugger="true" disableClientData="false" />
<site name="website" virtualFolder="/" physicalFolder="/" rootPath="/sitecore/content" startItem="/home" database="web" domain="extranet" allowDebug="true" cacheHtml="true" htmlCacheSize="10MB" registryCacheSize="0" viewStateCacheSize="0" xslCacheSize="5MB" filteredItemsCacheSize="2MB" enablePreview="true" enableWebEdit="true" enableDebugger="true" disableClientData="false" />

You can find this information on the Sitecore site as well: http://sdn.sitecore.net/faq/administration/live%20mode.aspx

Cool, any pitfalls though ?

Keep in mind that you are not working with Sitecore as it is meant to be used.
Sitecore tries to cache a lot of the renderings and content managed within Sitecore.
Sitecore caches are cleared when a publish event takes place. Since the live mode removes the need for publishing, these caches are no longer cleared. this is no problem on development servers since deploys reboot.

Also, keep in mind that specific search indexes with lucene will also include itemms that have publishing restrictions set. 

Comments

Post a Comment

Popular posts from this blog

Stupid exception: Device is not ready – System.IOException .net

-
When installing a Sitecore implementation from an development server environment to my laptop I ran into an absolutely stupid error. And it's great to have this kind of errors pop up from time to time even if you have been in the development world for so long and are still unable to fix it immediately. So, what error did I get? Device is not ready – System.IOException .net That is right... Nothing at all related to Sitecore. But then you start to doubt that as my stacktrace showed to Lucene [IOException: The device is not ready. ] System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) +1091 System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost) +1413 System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost) +92 Sitecore.IO.FileUtil.EnsureFolder(String path) +128 Sitecore.ContentSearch.LuceneProvider.LuceneIndex.CreateDirectory(String folder) +100 Sitecore.Co...
Read more

Date Ranges in C#

-
DateRange utility class Throughout development there are a number of typical things that tend to recur. One of these is implementing a means to display start and end dates for News, Events, Symposiums, Lives etc etc Writing a little class that manages printing these dates seemed like a necessary task that just had to be done in order to make this tedious task be a thing of the past. Therefore I created my "DateRange" class (what's in a name) that should handle this entirely for you. The Idea The intriquities of displaying a datetime range should be an abstraction. You should only need to worry about passing the correct dates (start and end - if applicable) to the Utility class combined with an optional formatting. The class can be entirely configured through use of Enumerations for all the separate settings such as DayFormat etc. An additional class was used to implement this utility, the StringValue attribute class. You can easily use thie class to a...
Read more

Sitecore 8.2 in-depth preview + 8.3 update info and Sitecore Ecommerce information

-
Image
During the last Sitecore User group session here in Belgium, Ryan Donovan was featured as the central speaker. The following two topics were on the agenda: Sitecore Commerce An in-depth information on 8.2 and 8.3 I was impressed by the drive behind Ryan and his team(s). It emphasized the drive that is pushing Sitecore forward. Sitecore is putting a lot of effort in producing well hardened and tested product releases that bring new features and rich applications. Sitecore Commerce Previous Sitecore commerce solutions were structured around either SCpbCS and SCpbMD. However, the vNext commerce product has been newly developed from the ground up. Previously, the commerce solution focussed itself around the architecture of Commerce Server to provide and API, manage the products and to derive the entire feature set from. With this Commerce vNext solution, Sitecore has set forward the aspiration to become one of the market leaders in commerce. The fist aim is to focu...
Read more