Today, July 15th, 2014, we are pleased to release dotCMS Enterprise version 2.5.5. This minor release is primarily focused around fixes and improvements related to the dotCMS advanced feature: Push Publishing. The upgrade will improve stability, performance and configuration tools for dotCMS Enterprise customers that are working with Push Publishing. Customers that want to take advantage of publishing content in dotCMS from one instance to another will want to be sure to get this update. Here are some highlights of the upgrade.
Editors Note: dotCMS 2.5.6 was released almost immediatley following 2.5.5. It fixes a problem with saving new containers after upgrading from dotCMS 2.x to 2.5.5. Systems running version 2.5.4 or below should upgrade straight to 2.5.6 to avoid the problem saving new containers. Info on the dotCMS Community Forum is available here: http://dotcms.com/forum/?place=msg%2Fdotcms%2FstHyE7ai0Q8%2FftOQ3UuVWJMJ
Integrity Checker & Conflict Resolver - This is a new feature in the Publishing Environments tab (system/configuration/publishing environments) that allows users to check for and resolve conflicts that that may exist between servers. Use the Integrity Checker and Conflict Resolver when you are setting up or troubleshooting a Push Publishing configuration (best used before you push publish content). For example, the Integrity Checker & Conflict Resolver can identify folders, structures, and workflows that are mismatched and would cause a problem when push publishing.
For improved troubleshooting, a significant improvement was made in logging any Push Publishing errors that may occur. This is helpful for system admins in setting up and troubleshooting Push Publishing environments.
Also improved in dotCMS version 2.5.5 is the ability to handle multi lingual content while Push Publishing and errors when content doesn't have a corresponding version in the default language. Additionally, problems related to using Push Publishing with Templates and Workflows have been resolved.
The 2.5.5 update also improved the performance of the Tag Manager when working in other languages and improved the performance and stability of the re-index process. File Assets now have improved support for Unicode characters as well.
Important for developers building workflows, ActionID is now displayed for reference on the Workflow screen. Also resolved with this release - issues when adding comments that would occasionally throw an error, and caching problems when re-ordering navigation menus (navtoolcaching) were identified and resolved.
If you are not familiar with dotCMS Push Publishing you can learn a little more here or even better, give us a call (tel:+1-305-900-2001) or drop us a line and we’d be happy to arrange a demo, or tell you all about the power and flexibility of this advanced feature of dotCMS.
DotCMS version 2.5.5 is highly recommended for anyone working with Push Publishing or considering it. Users that are upgrading from 2.x can upgrade directly to 2.5.5 without any intermediate steps and for those that use the dotCMS autoupdater, you can use it to update to version 2.5.5.
You can find out more details about the version 2.5.5 upgrade by reading the release notes: http://dotcms.com/docs/latest/changelogs or, you can get all the technical happenings at https://github.com/dotCMS
Delivering an omnichannel customer experience is now considered obligatory, but does omnichannel mean you should be on every channel?
Gettysburg College build a set of skills for their students, and this is what they learned.
Voice of the customer programs are easy, and your customers love the customer experience you give them. Well, at least, you think they do. Here’s why VOC programs are important, and six ways to not fail at them.
Customer experience is far too important to be exclusively owned by the marketing department. Here’s how to burst your CX bubble and take part in the ultimate team sport — customer experience orchestration — in five steps.