Announcing Silverstripe CMS Recipe 4.6.1

The Silverstripe CMS Squad recently released Silverstripe CMS Recipe 4.6.1. This release does not include security fixes, but contains a range of bugfixes, and we encourage developers to update. Take a look at the changelog for more information.

If you encounter any issues with the new release, please raise an issue on GitHub , making sure to include the recipe version.

Thanks for maintaining this great software.

Could someone please explain the roadmap?

At the moment it seems like the longest support will be for version 3, even though 4.6.1 is current.
See https://www.silverstripe.org/software/roadmap/ .

We’re using SilverStripe 3 and are evaluating if it will be worth upgrading for us early to mid 2021. We’ll need to come up with an estimate of effort involved for budgeting.

Could someone please give us some guidance on how much time may be required by the upgrade and whether it is worth the investment given a more solid support end date?

Hi,

Version 4 support is definitely longer than 3.x. The current 3.x releases are already out of full support, and currently in limited support (Critical bugfixes and critical security fixes).

The 4.x family support dates are still to be confirmed according to that timeline, but it’s safe to say they’ll extend beyond the 3.x line (currently shown as mid-2022 for full support)

Short answer: Upgrade as soon as it is practical to do so. The 4.x line is still in active development, and will be much more likely to get support for enhancements / security improvements (including things like PHP8)

There’s some pretty good documentation to help upgrading SS3 to SS4.

It’s a bit tricker than normal, particularly different from upgrading SS2 to SS3.
Migrating assets was a key issue for us. SS4 does some fancy stuff where assets can be versioned , and made only accessible when logged in for example, so you can’t just drop the assets folder in where it was before. The documentation has a Sake (here) command that takes care of that (via the commandline). Also, you need to upgrade your LAMP environment to PHP 7 which is pretty different, use of namespacing conventions etc. But, it’s pretty worth it. Backend CMS is super fast, all the new clients have loved it so far.