Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.


SilverStripe 3.1.6 is now out

We've now released the latest version of the SilverStripe framework, version 3.1.6.

Posted in Open Source, Company

Tagged framework, release

Comments 4

by Damian Mooyman

Posted 26 August 2014

Read post

We've now released the latest version of the SilverStripe framework, version 3.1.6. You can download this straight away from our downloads page.

What's new in this version

It's been more than three months since our last stable release, but in that time we have reviewed and fixed a large number of usability issues and bugs, with 36 resolved tickets in 3.1.6, and a small number of new features.

We've added a new "Published pages" filter in the CMS, which allows content editors to get a quick look at what the live sitetree currently looks like.

We've also made debugging stuff in the CLI a little bit more attractive. Where Debug::dump() once spat out HTML in every context, we've now added CLI friendly formatting with colour coordination!


If you are using composer, upgrading is pretty simple. If you are linking to the 3.1.*-dev branch, you likely already have the update from the main branch, but if not a “composer update” will do the job.

If you are linked to a 3.1.* tag or development branch then update your composer.json as below.

"require": {
"silverstripe/cms": "3.1.6",
"silverstripe/framework": "3.1.6"

You can create a new web project to try out using our composer web installer

composer create-project silverstripe/installer ./webroot 3.1.6

Please note any issues you discover on our Github issue tracker for framework, cms, or the installer.

Post your comment


  • @Michal That is totally not the expected release date. Good spotting!

    Posted by Damian, 03/09/2014 5:19pm (10 years ago)

  • Hey @Todd, if you want to replace core classes you really need to use Injector.

    Use the below yml in your mysite/_config/config.yml

    ContentControllerSearchExtension: MyCustomClass

    You can also use Object::useCustomClass to achieve a similar effect, but the above is the preferred solution.

    Posted by Damian, 03/09/2014 5:18pm (10 years ago)

  • After upgrading to 3.6.1, it seems like the framework is no longer defaulting to using classes declared in the mysite/ director first. For example, I use my own ContentControlleerSearchExtension class. this had never been a problem. the system always used mine in place of the class located in the cms/search directory. After upgrading via composer and running a dev/build I get the following error:

    Fatal error: Uncaught exception 'Exception' with message 'There are two files containing the "ContentControllerSearchExtension" class:

    Is this an intended behavior change?

    Posted by Todd Valentine, 30/08/2014 6:26am (10 years ago)

  • On it says this version was released 18 Jun 2014, is that a date of first RC? Or just not updated? Cheers

    Posted by Michal Kleiner, 26/08/2014 11:51am (10 years ago)

RSS feed for comments on this page | RSS feed for all comments