We've just released Bolt 3.6.0 as a maintenance release with fixes and new features for all current Bolt 3.x websites. As you might've read we are busy working on Bolt 4, but that doesn't mean we'll stop maintaining and updating Bolt 3.x for the foreseeable future.

This release contains a number of 'under the hood' improvements, as well as two more "visible" new features:

"Timed publish" improvements

We've added a new, finer-grained cron option, allowing you to time the publication of new posts and pages to the minute. If you set up the Task Scheduler as documented, you should be good to go.

Collapsing Repeaters and Blocks

When you collapse a Repeater or Block field, the bar will show an excerpt from the first text field. Additionally, you can now re-order the sets inside Repeaters and Blocks by drag'n'drop.


You can now also make them more easily recognizable by assigning icons to them:


The full list of changes can be found in the changelog.

Installation Instructions

Detailed instructions can be found in the install section of our documentation site. It lists the various supported ways to install Bolt, including links to the pre-packaged distribution versions. If you want to get up and running quickly, use:

curl -O https://bolt.cm/distribution/archive/3.6/bolt-v3.6.0.tar.gz
tar -xzf bolt-v3.6.0.tar.gz --strip-components=1
php app/nut init

Composer create project:

composer create-project bolt/composer-install:^3.6 --prefer-dist

If you're upgrading from Bolt 3.1 or 3.2 to Bolt 3.6, there are a few caveats you'll need to take into account. See the release posting for Bolt 3.4 for instructions on how to update your sites smoothly.

Updating from previous Bolt 3.x sites to 3.6

The update itself is pretty straightforward. If you're using composer to update, set the following in your composer.json:

"require": {
    "php": "^5.5.9 || ^7.0",
    "bolt/bolt": "^3.6",
"minimum-stability": "beta",
"prefer-stable": true,

Then run composer update --optimize-autoloader and php app/nut init to update.

If you're on the CLI, but prefer to update using the distribution files, follow the instructions above.

comments powered by Disqus