Weblog entry #103 for simonw
See all weblog entries made by simonw.
#103
PHP 5.2 and dotdeb
Posted by simonw on Mon 6 Nov 2006 at 14:35
The good folks at dotdeb continue pushing out PHP5 and MySQL packages as if a big release deadline is approaching ;)
I rashly assumed that 5.1.6 to 5.2 was a minor point release update, did some basic testing which worked 100%, no if's or but's, rolled it out on one of our live webservers, and discovered all the fiddly bits.
The loader for ioncube encoded files used by a client needed updating to ioncube_loader_lin_5.2.so (a free download from http://www.ioncube.com/loaders.php).
The same client also (alas) uses URL includes in their PHP, which is now disabled by default (very wise) and re-enabled using the new "allow_url_include" directive. The fun here being that the error messages are similar to those for "allow_url_fopen", when if you include PHP code, rather than just pulling remote files, you need both enabled.
Better yet when you search for the error message;
include() [function.include]: Failed opening url
...the search engine I choose cheerfully gave me a list of other people who probably want to know what the solution is as well. Of course the release and migration notes tell you all about the "allow_url_include", but you only read them after you find something is broken. http://www.dotdeb.org/news (re: Major release PHP 5.2.0).
Note to self, move this clients website to the test server except that would break the licencing that I want to test, now I remember why I like free software....
I rashly assumed that 5.1.6 to 5.2 was a minor point release update, did some basic testing which worked 100%, no if's or but's, rolled it out on one of our live webservers, and discovered all the fiddly bits.
The loader for ioncube encoded files used by a client needed updating to ioncube_loader_lin_5.2.so (a free download from http://www.ioncube.com/loaders.php).
The same client also (alas) uses URL includes in their PHP, which is now disabled by default (very wise) and re-enabled using the new "allow_url_include" directive. The fun here being that the error messages are similar to those for "allow_url_fopen", when if you include PHP code, rather than just pulling remote files, you need both enabled.
Better yet when you search for the error message;
include() [function.include]: Failed opening url
...the search engine I choose cheerfully gave me a list of other people who probably want to know what the solution is as well. Of course the release and migration notes tell you all about the "allow_url_include", but you only read them after you find something is broken. http://www.dotdeb.org/news (re: Major release PHP 5.2.0).
Note to self, move this clients website to the test server except that would break the licencing that I want to test, now I remember why I like free software....