In a hurry? Just change the PHP version in production like so:
- In the fortrabbit Dashboard
- navigate to the App and then click on Settings > PHP
- Change to a newer PHP version and hit "save".
- Check if your website is still working after a few minutes.
- You can safely switch back the version if it doesn't work (see below).
If the above procedure is breaking your website or you don't want to risk your production environment, here is a better, more sophisticated way:
- Update your local development environment to make sure everything works
- Push changes
- Change PHP version with our Dashboard (like described above)
Please see our old PHP upgrade path article, it was written for an older PHP version upgrade, but the steps are basically the same.
We plan to force-update all Apps still running on
PHP 7.1 to
PHP 7.2 in January 2020. The exact date will be announced. So you plenty of time ahead to implement the changes yourself.
Potentially asked questions
Which software version do I need to update to?
Sometimes it is difficult to find the time to upgrade an old project. Maybe you can come by with just a patch update without too much hassle? This is difficult to answer, projects rarely specify if their older releases support PHP 7.2, also there are plugins and custom code. But here are some we know of. The following versions refer to major version, upgraded to the latest minor and patch releases (major.minor.patch).
- Laravel: version
4 and5 will run on PHP 7.2
- Symfony: version 2, 3 and 4 will run on PHP 7.2
- Craft CMS: version 2 and 3 will run on PHP 7.2
- WordPress: version 4 and 5 will run on PHP 7.2
To which PHP version shall I update?
Upgrade to PHP 7.3 if possible. The lowest version you need to update now is to
PHP 7.2, but there are only minor differences between
PHP 7.2 and
PHP 7.3, it's likely that your App also runs on
PHP 7.3, so try the bigger jump right away.
Why we need to do this?
Sorry, PHP deadlines are not set by us, see php.net. We can not risk to run unsupported PHP versions much longer for security reasons.
Why we can't do it for you?
It's your code, your website. You need to make sure that the project will run with a newer version of PHP. We can not do that for you. We don't know your software and the inner workings of it. Check our support policies again please.
How can I test my code?
Please check out our old PHP testing article highlighting strategies and tooling to test your code for issues.
What about mcrypt?
A prominent change from
PHP 7.1 to
PHP 7.2 is that the popular mcrypt extension was removed. See php.net for details. So you can not enable that extension any more here.
With a framework or CMS that should not be your concern. It's either already on OpenSSL or a polyfill like mcrypt_compat is used.
Thanks for taking the time to keep your software up-to-date. Have a question? Don't hesitate to ask us right away! We can also offer you some discount for running two versions of your Apps side by side.