CrafterCMS 3.1.8
Released July 1, 2020
New Features
Added a new processor
s3DeploymentEventsProcessor
that uploads the deployment-events.properties of a site for S3 serverless deployer
See S3 Deployment Events Processor for more information.Added a new processor,
gitUpdateCommitIdProcessor
, that only updates the latest commit id
See Git Update Commit Id Processor for more information.Added a new property
updateCommitStore
for thegitDiffProcessor
that indicates whether or not to update the processed commit
See Git Diff Processor for more information.Added a new property
failDeploymentOnFailure
for all processors that enables failing the deployment when there’s a processor failure See Deployer Processors Guide for more information.Added support for automatically updating ES index settings
Whenever the Elasticsearch index settings are updated, for example, a new field has been added for a release, the ES index settings will be automatically updated by the CrafterCMS upgrade manager. The updated index containing the new settings will be named the current index version name incremented by 1, e.g. let’s say the current index ismysite-authoring_v1
, after the upgrade, the new index will now bemysite-authoring_v2
The ES index settings will be automatically updated when upgrading to CrafterCMS 3.1.8 for users upgrading from CrafterCMS 3.1.6 and earlier, and also for users upgrading from CrafterCMS 3.1.7 where a manual update of the ES index settings has not been performed. The automatic update is triggered when upgrading to 3.1.8 as mentioned above because of an update in the ES index settings (input fields tokenize in repeating groups) in CrafterCMS 3.1.7.
Updates
Elasticsearch improvements
The Elasticsearch client connection timeout, socket timeout and number of threads to use are now configurable for Studio, Engine and DeployerIn Studio, go to
CRAFTER_HOME/bin/apache-tomcat/shared/classes/crafter/studio/extension/
, then edit the studio-config-override.yaml file and update the following properties to the desired values# The connection timeout in milliseconds, if set to -1 the default will be used studio.search.timeout.connect: -1 # The socket timeout in milliseconds, if set to -1 the default will be used studio.search.timeout.socket: -1 # The number of threads to use, if set to -1 the default will be used studio.search.threads: -1
In Engine, go to
CRAFTER_HOME/bin/apache-tomcat/shared/classes/crafter/engine/extension
, then edit the server-config.properties and update the following properties to the desired values:# The connection timeout in milliseconds, if set to -1 the default will be used crafter.engine.elasticsearch.timeout.connect=-1 # The socket timeout in milliseconds, if set to -1 the default will be used crafter.engine.elasticsearch.timeout.socket=-1 # The number of threads to use, if set to -1 the default will be used crafter.engine.elasticsearch.threads=-1
In Deployer, edit
CRAFTER_HOME/bin/crafter-deployer/config/base-target.yaml
and update the following to the desired values:timeout: # The connection timeout in milliseconds, if set to -1 the default will be used connect: -1 # The socket timeout in milliseconds, if set to -1 the default will be used socket: -1 # The number of threads to use, if set to -1 the default will be used threads: -1
Lots of other small enhancements and bug fixes :)
For a full list of tickets, please visit: GitHub 3.1.8 Milestone
Important
Please see Upgrading CrafterCMS for instructions on how to update your CrafterCMS install to 3.1.1 (applies to 3.1.8)
For Docker/Kuber deployments, see Docker/Kuber Instructions for Upgrading CrafterCMS
For Linux installs, the embedded MariaDB upgrade requires the library libaio
which is not installed by default in some Linux distributions. Please see the section on Linux Prerequisites in Linux Prerequisite for instructions on how to install the library libaio
Please see Upgrade Notes for Fixing Backup Error for some important notes when updating to CrafterCMS 3.1.8