does that stand a reasonable chance of not blowing up in my face?
where should be a problem? your changed configs are saved as .rpmsave as everytime while deal with rpm
I discovered that one of my older websites flat out won't work with php 5.3 and requires a vey complex upgrade. meh.
It might not be _as_ bad as you think.
We made the push to php5.3 on a few web hosts and I got the fun job of fixing some old code for customer CMSes. Tail the site/vhost's error_log and fix the broken items. Once I took care of a few sites, I had a pretty comprehensive list that made further sites easy.
If you're adventurous, I could toss you a quick list of common items that need fixed.
---~~.~~--- Mike // SilverTip257 //
On Mon, Oct 15, 2012 at 4:34 AM, John R Pierce pierce@hogranch.com wrote:
does that stand a reasonable chance of not blowing up in my face?
where should be a problem? your changed configs are saved as .rpmsave as everytime while deal with rpm
I discovered that one of my older websites flat out won't work with php 5.3 and requires a vey complex upgrade. meh.
-- john r pierce N 37, W 122 santa cruz ca mid-left coast
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Am 15.10.2012 um 17:09 schrieb SilverTip257:
It might not be _as_ bad as you think.
We made the push to php5.3 on a few web hosts and I got the fun job of fixing some old code for customer CMSes. Tail the site/vhost's error_log and fix the broken items. Once I took care of a few sites, I had a pretty comprehensive list that made further sites easy.
If you're adventurous, I could toss you a quick list of common items that need fixed.
http://php.net/manual/en/migration53.php
-- LF
On 10/15/12 8:09 AM, SilverTip257 wrote:
It might not be_as_ bad as you think.
We made the push to php5.3 on a few web hosts and I got the fun job of fixing some old code for customer CMSes. Tail the site/vhost's error_log and fix the broken items. Once I took care of a few sites, I had a pretty comprehensive list that made further sites easy.
If you're adventurous, I could toss you a quick list of common items that need fixed.
thanks, but no thanks. I hate the php language, I find its an abomination, sloppy, poorly structured, full of weirdnesses that lead to poor programming. the simple fact that code that worked on 5.2 is known broken on 5.3 alone is enough to condemn it. anyways, the last thing I want to be doing is mucking through ancient CMS code.