• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Upgrading to PHP 5.2.17

PTS

New Pleskian
Hello all, I'm pretty comfortable with CLI but I want to make sure I'm taking the right steps when upgrading to PHP 5.2.17. I have a few websites that I can't afford to go down because of an upgrade failure.

I've got Plesk 10.1.1 running on CentOS 5 with the atomic repository already installed. To update to PHP 5.2.17, I am assuming the first step is as follows:

yum update php

If I proceed to install the two new packages and upgrade 18 existing packages, what are my next steps if any?

Does MySQL need to be updated? Right now I get the following error in phpMyAdmin: Your PHP MySQL library version 5.0.77 differs from your MySQL server version 5.1.52. This may cause unpredictable behavior.

Other than that error, everything runs well.

Thanks in advance.
 
Thanks Igor, I did see that page after posting this thread. That said, I do have a questions about Steps 3 and 4.

Step 3) Replace the PHP 4 php.ini with PHP 5.2.x's (if applicable):
mv /etc/php.ini.rpmnew /etc/php.ini

Step 4) Replace the php.conf with the PHP 5.2.x php.conf (if applicable):
mv /etc/httpd/conf.d/php.conf.rpmnew /etc/httpd/conf.d/php.conf


I'm upgrading from PHP 5.1.x so I assume Step 3 isn't applicable. What are you recommendations for Step 4? How do I know it it's applicable or not.

Thanks again.
 
I think it would be better contact atomicturtle user on this forum regarding their solution :)
 
Great question, the simple answer is if /etc/httpd/conf.d/php.conf.rpmnew exists then you probably need to do step 4.
 
Back
Top