Updating PHP from 5.2.6 to 5.3.2?

[GioMac]

http://patch-tracker.debian.org/package/php5/5.3.1-5

no way man, they have no patches for it
you MUST have problems with wordpress

[gOOvER]

**removed outdated URL**
works without problems

Where have you problems?? Maybe i can reproduce

[s2000tim]

it's me again. i updatet php to 5.3.2 and mysql to 5.1.44. when i want to log in into ispcp i get this message:

Warning: idn_to_ascii() expects parameter 2 to be long, string given in /var/www/ispcp/gui/include/ispcp-functions.php on line 374

Warning: idn_to_ascii() expects parameter 2 to be long, string given in /var/www/ispcp/gui/include/ispcp-functions.php on line 374

i got the php package from dotdeb.org
apart from that my website runs without problems.

[GioMac]

(03-29-2010 07:43 PM)gOOvER Wrote:  works without problems

Where have you problems?? Maybe i can reproduce

strange...

s2000tim
http://isp-control.net/forum/showthread....=7513&pid=

[bulforce]

This was done on debian lenny 32bit

Add this lines in your /etc/apt/sources.list

Quote:deb http://php53.dotdeb.org stable all
deb-src http://php53.dotdeb.org stable all

Issue command:

Quote:# apt-get update

Update php to 5.3.2

Quote:# apt-get install php5

It works for me... so far!

Will get back if problems appear.

Update:

It seems that after logout... I couldnt log in due to error in idn_to_ascii() built in function. I checked the manual regarding this function and seems that the second parameter is optional, so i removed it

here is the encode_idna() from ispcp-functions.php that worked for me.

Code:

function encode_idna($input) {
        if (function_exists('idn_to_ascii')) {
                //return idn_to_ascii($input, 'utf-8');
                return idn_to_ascii($input);
        }

        $IDN = new idna_convert();
        $output = $IDN->encode($input);
        return $output;
}

Next thing is that the date() throws errors due to default time zone not being set. I decide to set that in the php.ini so it will be applied globally over the whole ispcp gui

Uncomment date.timezone and put your timezone in /var/www/fcgi/master/php5/php.ini

Code:

date.timezone = "America/New_York"

next error

Quote:Deprecated: Function split() is deprecated in /var/www/ispcp/gui/include/phpsysinfo/common_functions.php on line 169

Deprecated: Function split() is deprecated in /var/www/ispcp/gui/include/phpsysinfo/class.Linux.inc.php on line 116

fix it by replacing the deprecated function split() with explode()

Thats so far... if I see something else will post back

[sseitz]

Quote:Next thing is that the date() throws errors due to default time zone not being set. I decide to set that in the php.ini so it will be applied globally over the whole ispcp gui

Uncomment date.timezone and put your timezone in /var/www/fcgi/master/php5/php.ini

Code:

date.timezone = "America/New_York"

I'ld suggest to set the timezone systemwide for any php process (including cli calls) to avoid potential problems with e.g. cronjobs. Better add this line into a file placed in /etc/php5/conf.d/ like /etc/php5/conf.d/datetimezone.ini

[RatS]

Thank you for your report!

(04-05-2010 10:27 AM)bulforce Wrote:  It seems that after logout... I couldnt log in due to error in idn_to_ascii() built in function. I checked the manual regarding this function and seems that the second parameter is optional, so i removed it

here is the encode_idna() from ispcp-functions.php that worked for me.

I will check this.

(04-05-2010 10:27 AM)bulforce Wrote:  Next thing is that the date() throws errors due to default time zone not being set. I decide to set that in the php.ini so it will be applied globally over the whole ispcp gui

There is a ticket open #2053 to handle this issue.

(04-05-2010 10:27 AM)bulforce Wrote:  

Quote:Deprecated: Function split() is deprecated in /var/www/ispcp/gui/include/phpsysinfo/common_functions.php on line 169

Deprecated: Function split() is deprecated in /var/www/ispcp/gui/include/phpsysinfo/class.Linux.inc.php on line 116

phpSysInfo will be removed with ispCP Omega 1.0.6

Could you please additionally check if ticket #1910 is valid or not. If two confirm that it is not, we can close the ticket. Thanks!