Initial compatibility testing and risk management
Posted: Tue Apr 22, 2025 5:22 am
That's why the transition to PHP 8.2 was both important and complex. While new websites on our servers have been using PHP 8.2 by default since May 2024, updating all sites using our managed PHP service required a meticulous approach.
In July, we began a phased upgrade process for customers using our rcs data japan managed PHP service. We started with the first shared server test and performed detailed tests with websites to verify that they loaded correctly with PHP 8.2. These tests were conducted in isolation so that customer sites would not be affected by the evaluation process.
This type of testing helped us understand whether sites were ready for PHP 8.2. Our comprehensive compatibility checks helped us categorize websites into low-risk and high-risk groups to better manage the transition and reduce potential risks for customers.
Low risk : Websites that our tests identify as working correctly with PHP 8.2.
High risk : Websites for which we have detected compatibility issues.
For all sites that loaded without issues, we sent a notification one week before the actual update, ensuring complete transparency and avoiding any surprises for our customers. For sites that did not pass the compatibility test, we kept them running on PHP 7.4. This allowed customers to update their site code to ensure compatibility while remaining fully functional.
We also contacted these customers to recommend that they revert to managed PHP once the compatibility issues were resolved, so that we could continue to update their sites automatically and save them time and effort.
In July, we began a phased upgrade process for customers using our rcs data japan managed PHP service. We started with the first shared server test and performed detailed tests with websites to verify that they loaded correctly with PHP 8.2. These tests were conducted in isolation so that customer sites would not be affected by the evaluation process.
This type of testing helped us understand whether sites were ready for PHP 8.2. Our comprehensive compatibility checks helped us categorize websites into low-risk and high-risk groups to better manage the transition and reduce potential risks for customers.
Low risk : Websites that our tests identify as working correctly with PHP 8.2.
High risk : Websites for which we have detected compatibility issues.
For all sites that loaded without issues, we sent a notification one week before the actual update, ensuring complete transparency and avoiding any surprises for our customers. For sites that did not pass the compatibility test, we kept them running on PHP 7.4. This allowed customers to update their site code to ensure compatibility while remaining fully functional.
We also contacted these customers to recommend that they revert to managed PHP once the compatibility issues were resolved, so that we could continue to update their sites automatically and save them time and effort.