PHP 5.2 to PHP 5.3

[bada_bing]

We received a message from our hosting provider that they upgrade from PHP 5.2 to PHP 5.3 and things broke on our vbulletin site, assumption its some plugin's we are running so they had to revert back to PHP 5.2 . They are allowing us some time to correct this and make sure any plugins we are running will work for PHP 5.23, what is the best way to find plugins that wont run in PHP 5.2 ?

Has anyone ran into this issue and what did you do to correct it. I would hate to loose any important plugins because of PHP version incompatibility

Thanks

[Lynne]

Try reading the modification threads. A while ago (last summer or a bit before?), some hosts started upgrading a bunch of servers to 5.3 and several users using vbulletin versions less than 3.8.5 start posting about errors. I'm sure they would have posted in the modification threads around then if there were problems with the modifications.

[bada_bing]

Try reading the modification threads. A while ago (last summer or a bit before?), some hosts started upgrading a bunch of servers to 5.3 and several users using vbulletin versions less than 3.8.5 start posting about errors. I'm sure they would have posted in the modification threads around then if there were problems with the modifications.

I am running 3.87 though ?

[Lynne]

.3.8.7 is compatible with PHP5.3. But, as I said, if you want to find out if the modifications are, then read the threads and see if anybody has complained about any problems with PHP5.3.

[snakes1100]

Ive not seen any hack on here for 3.8.7 that didnt work because of php 5.3.xx, first you need to have them upgrade php back to 5.3.xx, then start trouble shooting via logging or displaying php errors on site.

You will see a numerous hacks/addons spit out deprecated code, but i havent see that stop their functionality either.

[DivisionByZero]

just wait until they jump the gun and start upping servers to 5.4 :-\

[CoffeeLovesYou]

Well,
I know when we first got 5.3, some products broke that were using TYPE=MyISAM. Had to change it to ENGINE=MyIsam, or something.
Also, we were getting some errors at the top of the forum that had to do with 2 files in our includes folder, and it required removing? or adding a & infront of some of the equal (=) signs.

[squidsk]

Well,
I know when we first got 5.3, some products broke that were using TYPE=MyISAM. Had to change it to ENGINE=MyIsam, or something.
Also, we were getting some errors at the top of the forum that had to do with 2 files in our includes folder, and it required removing? or adding a & infront of some of the equal (=) signs.
That's a mysql error when upgrading to mysql 5.1, as mysql 5.1 no longer supports using TYPE=X, so that has nothing to do with php.

[CoffeeLovesYou]

That's a mysql error when upgrading to mysql 5.1, as mysql 5.1 no longer supports using TYPE=X, so that has nothing to do with php.
k, but second part did have to do with a PHP version change

[snakes1100]

Those are simply deprecated error messages, which i stated in my initial post, it doesnt mean the hack wasnt working, its simply a message displayed by php to let you know your using old php coding & it should be updated.

display_errors = Off