Doc tools: Log in
We have sadly noticed that some users have not yet updated their websites and applications to support PHP 7. As we've moved to PHP 7 during the weekend of the 25th and 26th of June 2016, some websites have stopped working.
To help users that are still using versions of web applications or CMSes that don't support PHP 7, or are making the transition to a new application, we have decided to temporarily offer a PHP 5.5 server. Users are free to temporarily point their websites to the address of this server to update their applications and CMSes (like Wordpress, Drupal or Joomla, including plugins, modules, extensions and themes) or to move content from an old website to a new one.
The PHP 5.5 web server is available on
188.8.131.52. You can tell your machine to use that IP address for your website on your local computer by changing the hosts file.
On Windows: if Windows is installed in
C:\Windows (the default), this will be
On Mac OS X:
If your website is at
username.studentenweb.org, then you can point your website to the PHP 5.5 server by adding the following line to your hosts file:
184.108.40.206 username.ulyssis.be username.studentenweb.org
Of course, if you use your own domain (.be, .org, .com) you can use that.
Make sure to remove these changes when you're done.
You can easily switch between the PHP 5.5 server and the regular PHP 7 servers by changing your hosts file.
Don't forget to update all aspects of your application. In case of Wordpress or another CMS, make sure that you not only update the system but also the different plugins, modules or extension and any kind of themes or templates.
If your application still does not work on the regular servers after updating it, confirm that they actually offer PHP 7 support. Some web applications, such as CiviCRM, are still working on PHP 7 support. If that's not the problem, please refer to your log files. Instructions on how to do this can be found on Getting Apache logs and Managing PHP errors.
If problems persist, you may contact us at firstname.lastname@example.org, but be sure to try by yourself first. While we do wish to help people with persisting issues, we're not responsible for keeping your CMS updated.