• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/

PHP Problems

If he's using PHP 5.1.6 than he's probably on RHEL 5 or CentOS. I doubt that PHP is corrupt, but if it is, I'd try reinstalling the RPM.

Switching to ART's PHP is not bad per se, but you need to understand what this means to your server, upgrades, etc. before you do it.
 
I used php 5.2.5 - once used ART's build, and once using a custom build I made and both times it $#@'ed up my server. Reverting back to php 5.2.3 fixed all the problems that 5.2.5 introduced.

before upgrading to 5.2.5 make sure to test it to see if it will work for your customers.
 
In response to the 'php_admin_value' problems - I did this to get rid of everything

in vhost.conf files
Code:
grep 'php_admin_value' /var/www/vhosts/*/conf/vhost.conf > php-admin-value-vhost.report
for i in `cat php-admin-value-vhost.report | awk '{ print $1 }'`; do
FILE=$(echo $i|sed 's/:/ /g')
sed 's/php_admin_value/php_value/g' $FILE
done

In .htaccess files
Code:
grep 'php_admin_value' `locate '.htaccess' | grep /var/www/vhosts/` > php-admin-value-htaccess.report
for i in `cat php-admin-value-htaccess.report | awk '{ print $1 }'`; do
FILE=$(echo $i|sed 's/:/ /g')
sed 's/php_admin_value/php_value/g' $FILE
done

Seemed to get rid of everything fairly nicely.
 
In response to the 'php_admin_value' problems - I did this to get rid of everything

in vhost.conf files
in .htaccess files


but what is with all the entries in the httpd.conf-files plesk is writing?
 
Back
Top