Below is the changelog for the dotCMS releases, which includes new features and information regarding major changes in the software. Looking to drink from the firehose? See the complete dotCMS changelog in GitHub.
2.0
Released: May 3, 2012
Overview of Changes
New Customizable/Extendable Workflow Engine (Enterprise)
- Allows the creation of multiple, muli-level workflow schemes for content and files.
- Workflows can trigger customizable chain of sub-actions, called Actionlets. Examples of what can be done with Actionlets include posting a value of a content field to a twitter account on publish or adding or removing a document/piece of content to a SOLR index on publish/unpublish, etc...
- Different content type can have different workflows.
Files as Content (Community & Enterprise)
- New file types can be created, fields can be customized on a per filetype basis.
- URL addressable binary files with all the benefits of being content.
- CDN friendly pathing to image manipulation with no query strings.
- Greatly improved Multi-file uploads
- Workflows can be applied to files based on their content types. So your photo library can have one type of workflow vs. your document library.
Full-Text and Metadata Extraction/Indexing (Enterprise)
- Metadata/content is extracted from files and is indexed and made searchable, including full-text indexing. This allows for document management solutions to be created using the dotCMS platform.
ElasticSearch for performance and horizontal scalability (Community & Enterprise)
- Index Replication/Auto-sharding
- Index once, available everywhere in clustered installations.
- Allows index infrastructure to scale separately from dotCMS installation based on an implementation’s need.
- Index shipping - Indicies can be backed up and restored across instances
Admin Tooling Improvements (Community & Enterprise)
- The CMS Maintenance UI now has an Index Manager
- Restful Access to manage dotCMS Indicies
Pessimistic Content Check-in / Checkout (Community & Enterprise)
- Content can be locked for editing - only the editing user or CMS Administrators can release the lock.
Content Editing UI improvements (Community & Enterprise)
- Workflows and content locking are integrated into an improved content editing UI.
Key/Value Field Type (Community & Enterprise)
- Allows a content type an unlimited number of values that can be determined when the content is being entered – think the specifications page for various electronic products in an ecommerce environment.
Data Model/API Improvements (Community & Enterprise)
- Content state has been moved to a separate table
- Identifiers, live and working versions all enforced by referential integrity
Plugin Improvements (Community & Enterprise)
- There is now a ROOT folder that can be added to plugins which can override ANY file in dotCMS. We recommend using this folder in the com.dotcms.config plugin (./plugins/com.dotcms.config/ROOT) to maintain any local changes to your /bin/startup scripts and tomcat's .xml configuration files.
OSGI Implemented(BETA) (Community & Enterprise)
- You can now HOT deploy Viewtools, Actionlets(Custom Workflow Actions) and other OSGI packages via OSGI without restarting your dotCMS installation.
- Initial beta of OSGI UI Portlet and Tooling
Spring 3 MVC Support (Community & Enterprise)
-
dotCMS 2.0 ships with a Spring 3 View and View Resolver. This means that developers looking to implement controller logic in their CMS or content driven apps can use Spring MVC to implement their functionality in dotCMS.
For more information, see this
blog post.
Autoupdater (Community & Enterprise)
- The Auto Updater is improved and provides an easier folder structure to support updating
- Post 2.0 you will be able to download updates directly and use the Auto Updater to patch
Velocity Logging Improvements (Community & Enterprise)
- You can now see a stacktrace of templates for velocity errors
Things to Know
-
2.0 is a MANUAL upgrade from the 1.9 series; the 1.9 Auto Updater cannot be used to perform the upgrade.
-
The Nutch based site search functionality has been removed because of library conflicts with the new Elastic Search libraries. For our Enterprise customers, there will be a much improved site search in the next release (already working in the lastest code in GitHub). For smaller sites and community members, we recommend using a hosted search provider such as Google Site Search, or setting up a standalone modern Nutch/Solr implementation and integrating with that.
-
Lucene based content pulls and ordering
The new elastic search lucene implementation is much less forgiving about the "order by" clause in content pulls. If you do not see results for content pulls in your velocity code, make sure your order by clause has the structure name . the field name, e.g. "news.publishDate desc" rather than just "publishDate". When in doubt, try using the "moddate" to test that your lucene pulls are working.
-
Category Groups have been removed
We no longer support the long-depricated idea of "Category Groups". Categories are obviously still supported.
-
The ZIP distibution of dotCMS is now packaged differently to work with the new Auto Updater. You now have a ./dotserver directory which is the dotCMS itself and a ./autoupdater directory.
In addition to these directories, ./backups from the Auto Updater will be stored at the same level as the ./dotserver directory. You can clean these backups as you need/desire to.
-
There is no need to touch any file under the ./dotserver directory to config dotCMS. Use the new plugin /ROOT directory for your startup and tomcat config files and you can maintain them separate from dotCMS across version updates.
For information on how to upgrade to dotCMS 2.0 please review our documentation: Upgrading to dotCMS 2.0
1.9.5.0
Released: Feb 28, 2012
Overview of Changes
- Streamlined cache infrastructure based on a non-blocking LRU algorithm. You now have control of what gets cached to disk and what does not.
- You can now see how much memory each Cache region consumes in the UI along with other important cache stats.
- Fixed multiple JS and Browser related issues.
- Improved CAS and LDAP support.
- Internationalized the JSON/XML Servlet.
Full Changelog
http://jira.dotmarketing.net/secure/ReleaseNote.jspa?projectId=5803855&styleName=Html&version=10132
1.9.4.2
Released: Dec 1, 2011
Fixes
- FIxed some Browser issues with the Category Manager and some issues with Categories and special characters during Import/Export
- Fixed an issue with Required Categories on Calendar Events
Changelog
1.9.4.1
Released: Nov 16, 2011
Fixes
- Fixed am issue that would cause relationships to not order properly on save or adding of related content
- Fixed some issues with special characters and 1.9.4 Tag Upgrade
Changelog
1.9.4.0
Released: Nov 8, 2011
Improvements
- Category Manager UI completely redone
- Category Field UI on Edit Content screen is redone
- Tag Manager
- Tags can now be Global OR Host Specific
- Dutch Translation Improved
- Added ability for Cache to invalidate without using the DB in a cluster. This is huge for clusters which get backend load.
Fixes
- Fixed an issue which could remove the language files when cleaning old assets
- Fixed a few Hardcoded Strings which prevented translation/li>
- Some IE8 Issues
- Improved the query translator which translated queires using the 1.7 syntax
- Some Permission Fixes when obects where inheriting from a Folder or Host
- Log4j Improvements. There was a possible Syncronization issue which could slow sites down under load
- A few WebLogic fixes
- Removed some syncronized code which could cause slow down under load`
Things to know
- All legacy eCommerce functionality built into dotCMS has been deprecated and will be removed in an upcoming version.
Changelog
1.9.3.2
Released: Sep 13, 2011
Improvements
- Content can now be created via email (see documentation).
- Fields can now have variables associated with them - will be used for future development.
- Backend now translated into Dutch thanks to Koen Peters and Isaac.nl!
Fixes
- Fixed issue with related content which shared a field name
- Improved relationship importing
- XSS fixes
- Fixed Tab Divider on events
- Fixed issue where dotCMS gave an error when only one language
- Continued improvements to permissions
- Performance tweaks to $dotcontent.pull
- Fixed issues with JBOSS AS deploy
- Copy Event now works properly
- A number of stability and performance tweaks
Things to know
- All legacy eCommerce functionality built into dotCMS has been deprecated and will be removed in an upcoming version.
Changelog
1.9.3.1
Released: Jul 8, 2011
Improvements
- Improve UI/XP of content relationships
- Removed old school popups from content searches.
- IE 9 and FireFox 5 are fully supported in the backend.
- IE 6 and 7 are now supported through the use of the ChromeFrame Plugin.
- An Admin can now tail dotcms logs from the CMS Maintenance scree.
- The content importer now supports importing relationships (via a lucene query) and files
- The spell checker is now fully integrated into the WYSIWYG Editor
- Performance improvements for permissions
- LDAP will now auto create roles that do not exist
- For Enterprise clients, the TagCloud Macro now caches for 24 hours by default (can be overridden).
Things to know
- YOU MUST DELETE THE dotCMS/dotsecure/h2db DIRECTORY ON UPGRADE.
- YOU MUST DELETE THE dotCMS/html/js/tinymce/jscripts/tiny_mce/*.gz ON UPGRADE.
- You will need to DELETE YOUR BROWSER'S CACHE. Dojo has been upgraded to version 1.6. This is the main JavaScript library used by dotCMS and is also used on the front end form builder. Users might see inconsistencies and will need to flush all browsers caches.
- The default username/password on a clean install is now admin@dotcms.com/admin.
- This will be the last version of dotCMS that supports Java 5.
- Unused/Legacy portlets will be REMOVED in next version. This includes all eCommerce Tools, older Event management, "banners" and "jobs" mangagers.
- The Entity object, which drive the deprecated "Categories Field" type, will be REMOVED in the next version and should be replaced with the newer "Category" type moving forward.
Changelog
