Update (04/11/2019): The information on this page is now out of date. Please see the PHP version compatibility page for up to date information.
From 31 December 2018, PHP 5.6 is going into end of life support and will stop receiving security updates from the PHP community.
We will be emailing all CWP Stack Managers and Deployers so they are aware of what they need to do. However, if you are interested in learning more, read on!
Why should I upgrade to 7.1?
For security reasons, we must start transitioning off PHP 5.6. After December 2018, the PHP community will no longer support PHP 5.6. Click here(external link) for more information.
PHP 7.1 offers significant increases in speed on your site(s). It has been demonstrated, in some cases, to offer three times the speed of PHP 5.6.
Do I need to upgrade my PHP version myself?
No, you do not need to update your PHP version. We will upgrade your version of PHP for you once you have upgraded your CWP version. We will start with UAT and test environments and follow up on production shortly afterwards.
Which version am I on?
The next steps depend on which version you are on. You can find out which version you are on by checking your environments on the deployment dashboard.
If I have more questions after reading the below, who should I ask?
If you’ve got any further questions about this, please raise a helpdesk ticket via the CWP helpdesk.
If you are on CWP 1.6 or higher
SilverStripe will be upgrading CWP servers to PHP 7.1 before 31 December 2018. The CWP team will upgrade UAT servers running CWP recipe 1.6 and above to PHP 7.1 in early November and will notify your stack manager and deployer. This will provide you with a preview window for testing.
What do I need to do?
The PHP 7.1 upgrade to UAT will be scheduled with your Instance Manager.
Following the PHP 7.1 upgrade in UAT, please test that your site(s) work.
We know some clients may not be able to fully upgrade all sites by 31 December 2018. In this situation, we will be providing an extended support window.
Please contact us at the CWP helpdesk if there are any issues.
What else can I do to prepare for this upgrade?
You can choose to enlist a developer to run test your application with PHP 7.1 locally.
If you are on CWP 1.5 or lower
PHP Extended Support window
We are aware that some clients may not be able to upgrade all of their sites by December 2018. In order to safeguard any sites remaining on PHP 5.6, we will be extending the window with community long term support packages. If necessary, this will give you more time to upgrade your site. SilverStripe will stop supporting PHP 5.6 completely on 30 June 2019.
What do I need to do?
The best way to maintain the performance and security of your Instance(s) is to upgrade your CWP recipe to version 1.6 or higher, and your SilverStripe Framework to version 3.6 or higher, as these versions are compatible with PHP 7.1.
Upgrade your CWP recipe to version 1.6 or higher, and your SilverStripe Framework to version 3.6 or higher, as soon as possible before the extended support ends on 30 June 2019.
- A modern and responsive user interface
- Better versioning and asset handling
- Flexible content and data architecture
- Content blocks and updated themes
- New recipe structure
- Active development and full support
What if I require external developer support?
How long will my upgrade take?
Upgrading your site could take anywhere between two days to a number of weeks depending on the complexity of the codebase and which framework version is in place.
I want to upgrade early — how do I do that?
That is great news! We’d be happy to upgrade your stack early. Please raise a helpdesk ticket.
There is no way I can upgrade by December 2018 — what do I do?
We know some clients will not be able to upgrade by 31 December 2018. In order to safeguard services remaining on PHP 5.6, we will utilise the community supported long term support Debian packages. Plan your upgrade as soon as possible before the extended support period ends.
What is the final date I need to upgrade by?
The final date you must update by is 30 June 2019.