dotCMS

dotCMS was built upon the acclaimed Liferay portal.

It expands its features to support enterprise-level installations. mobile devices, and cloud-based deployment.

dotCMS is truly an all-encompassing solution when needing to deploy a website building toolkit on your servers.

It features a simple on-page editing system, themes, plugins, and lots of features that simplify the content management operations so even regular users can carry them out without too much instructions or technical skills.

The admin panel and the themes themselves are responsive, adapting to today's current mobile-friendly Web environment.

Developers are not limited to "pages" as in the classic CMS paradigm, but can manage "content types" which allows them to create a website for whatever they want without having to use plugins or add-ons for specific types of content.

There's also support for multi-user, multi-lingual and multi-site setups, just in case you want to cater for a wider userbase.

All in all, dotCMS is a professional solution for situations where a basic 5-10 page website is not gonna make the cut and you need a more complex website management platform at your disposal.

What is new in this release:

• Velocity Macro Caching
• The Startup Script Has Changed
• The log4j.xml File is No Longer Used
• Cache Configuration Has Changed

What is new in version 3.1:

• Pages can now exist on the root of a host. This means that if you have a page on the root of your site you no longer need the Virtual Link to map your home page
• Pages no longer require a file extension
• Pages can have UTF-8 URIs.
• Added a more secure Viewtool to query the dotCMS DB directly. The new tool is mapped to $sql. The old method in the CMSMacro Viewtool has been deprecated.
• All Enterprise versions have added the ability to pass Elasticsearch queries directly into dotCMS. This allows greater flexibility. The queries can be passed in via REST, directly to our APIs in Java, or from Velocity via a Viewtool
• HTML Pages are now Content

What is new in version 3.0.1:

• Fixed some typos in the backend
• Updated some missing files in the WYSIWYG editor that was causing issues with both workflows and front end content submission
• Addressed a leak from a possible closed connection while requesting a file
• Updated the helloworld plugin for 3.0
• Improved the logic when running a full reindex. Helps with those who run a reindex that never finishes

What is new in version 3.0:

• New Features:
• The License Management Tab in the UI is redone and improved
• In the new my.dotcms.com Support Portal you can get a License Pack which allows you to Autoscale
• Your ServerID and License Info is fully manageable in the License Manager
• Both SASS and LESS files will compile server side as you upload the source files
• The SASS/LESS files are cached server side so they only have to compile the first time they are hit
• Attaching 2 different dotCMS installs to the same DB and Assets will cause the 2 installs to cluster with zero config
• Network and Clustering config can now be done from the Configuration Manager in the Backend UI
• Third Party Jars now have unique packaging to avoid conflicts with plugins and app servers
• Getting a WAR file can now be obtained from the normal dotCMS download
• A shell and batch script to produce a WAR is included in the bin directory
• Added JSONP to REST APIs
• Area of the system like Push Publishing have had been improved with better logging to help diagnose issues
• A notification framework has been implemented complete with APIs to allow system wide communication and notifications
• The User Activity Logger is much improved and logs many more dotCMS user actions
• The dotCMS distribution can now be run without any config with the internal H2 DB
• H2DB is not intended for production use
• The index libraries have all been upgraded providing much improved indexing performance
• The Ace Editor is now used for all code textareas
• Code can now be added to a container for every structure. This allows a container to display content from multiple structures
• The XML Sitemap plugin is now included

What is new in version 2.5.6:

• Fixes:
• Addressed issue with saving containers after upgrade to 2.5.5.

What is new in version 2.5.4:

• Made forgotten password process more secure - now emails token for password reset.
• Increased security algorithm for generation of passwords.
• Fixed issue in Edit Mode which could resulting a 404 when clicking on a Menu Link.
• By default you cannot redirect to an external referrer. To change this default behavior, set DISABLE_EXTERNAL_REFERERS=false in dotmarketing-config.properties file of your configuration plugin.
• Increased security for comments functionality.
• Increased security to prevent header injection.
• Improved XSS prevention algorithms.
• Fixed live site caching issue when updating files.
• Fixed CSV import when importing to a host.
• Increased security of AjaxFileUploadServlet.
• Improved security for system user.
• Locked down multiple security issues.
• Turned off autocompletion of password fields.

What is new in version 2.5.3:

• Fixed multiple issues for WebSphere 8
• Fixed the Auto Login Checkbox
• Fixed multiple IE issues in the backend
• Fixed multiple errors in the browser's console in the backend
• Improved some system performance when running under load and during site search indexing
• Fixed a few Push Publishing Issues
• OSGi can now be disabled
• Tags will now be imported properly when loading users from a CSV file

What is new in version 2.5.2:

• Fixed concurrency issues with the dotcms cache under load
• OSGi Examples all use Gradle now for building. This makes deploying and building plugins much easier
• Fixed the issue where modifying files in a theme could cause the theme to disappear
• Improved the Upgrade from dotCMS 1.9 to 2.5.2+
• Fixed over 20 PUSH publishing issues

What is new in version 2.5.1:

• Workflows will now Push Publish when Pushing a Structure
• When Content is Pushed the Workflow will be maintained meaning you will be in the same step on the Receiving server
• When Pushing Structures the Field Variable name is now used for Fields which is important when the inodes are different but the Field Variable is the same

What is new in version 2.5:

• Easy browser-based administration - manage your remote servers and publishing process via an intuitive web based Administration UI.
• One and Two-way synchronization - Sync your content changes between servers in any direction to insure your Development, Testing and Production setups all have the latest data.
• Push Spring Web and OSGi applications - Remotely publish web applications, which can include Spring Web Apps, content, assets or code between environments.
• Scales to your needs - Push Publish anything from a single piece of content to an entire website.
• Scriptable deployments - Build downloadable, repeatable bundles that can be deployed (RESTfully) to multiple dotcms instances programmatically.

What is new in version 2.3:

• Themes provide a portable, sharable way to apply a common look and feel across a site or sites.
• dotCMS has standardized our starter site to leverage theme based layout on Twitter's Bootstrap for responsive design.
• Out of the box, dotCMS ships with 2 responsive, Bootstrap based themes.
• Themes can be shared within a host and across hosts.
• Themes are not tied to any CSS or JS Framework. Users can write themes that use any available HTML Frameworks.
• Allows basic users the ability to create dotCMS templates without any knowledge of HTML code.
• The Template Builder/Designer is used in conjunction with themes.
• Can use existing themes, create your own theme, or download a third party theme to create a new design template.
• The new Link Checker workflow automatically checks links in WYSIWYG content before saving it, to avoid external link errors.
• Also, there is a new portlet called Broken Links that can run an external link check on all content structures and creates a report of all broken links.
• This process can be scheduled using a cron expression, which then sends an email with the link errors found to the content editors.
• Users can now easily, reuse wiki content from TWiki, Media, Confluence, etc..