Hello,
Approximately a year ago I posted an entry where I was expressing concerns about PHP 5.2 end of life declared, while contributed modules for Drupal 6 were not yet PHP 5.3 compatible.
Now we see PHP 5.4 having been released, but when I tried to run a replica of some of my Drupal 6 sites under PHP 5.3.10, I still have problems due to deprecated API/function calls. I don't see major problems, the code seems working, but I would like to be absolutely sure code won't break on one of the next 5.3 versions (let alone 5.4).
Have anyone composed the complete picture of PHP 5.3 compatibility? Soon we will be really eager to know of PHP 5.4 and so on compatibility, so I suppose a procedure of assigning compatibility tags should exist, so that people could know what modules are compatible with what versions.
A PHP-related tag(s) (taxonomy term) assigned to a module (project) could be enough, as well as possibly introducing a field in .info stating the compatibility. That could help both developers and module users.
But I suppose that's a lot of work, both administrative and programming. I can just start contacting authors of modules, to draw their attention to possible problem.
If someone is already doing that/having done that, I would be also eager to assist.
Thanks.
Comments
PHP 5.4 Compatibility
Well, I can already attest that PHP 5.4.0 breaks a few modules in D6, haven't done a lot of testing in D7 yet, I would assume we will find the same problems there. The major issue we have found, is that PHP 5.4.0 has finally removed "call time pass by reference" it has been deprecated for a while, and we have been warned since PHP 5.2(??) that it was going away. It's gone, and thus any code using it will simply fail, it's no longer an option to just turn off the warning.
John
John W Smith
IT / IS Contractor
Impressions 1st Consulting
As far as I understand, most
As far as I understand, most compatibility problems can be found by running 'php -l' on all the PHP files of a module.
So, generally, it's relatively easy to find the modules that are most likely to break.
Konstantin Boyandin
System administrator & Web programmer
Email: konstantin at boyandin dot com
Modules testing
I'd like to see core, and all modules, include a PHP version compatibility icon. Perhaps the use of "php -l" lets this be done semi-automatically.
It would also be useful if the Update and Upgrade modules also included this information, so you could see at a glance whether an installation will work if PHP is upgraded.
we can check it by running
we can check it by running 'php -l' on all the PHP files of a module.
go through:
http://www.phpzag.com/php/
It can only find syntax
It can only find syntax incompatibilities.
It won't report about functions that behave differently. Thus, the test isn't sufficient.
Konstantin Boyandin
System administrator & Web programmer
Email: konstantin at boyandin dot com
'php -l'
Notes: 'php -l' is simply a very basic 'lint' check for code!
--
Linux: Web Developer
Peter Bowey Computer Solutions
Australia: GMT+9:30
(¯`·..·[ Peter ]·..·´¯)
If every module had an icon
If every module had an icon which showed whether it was known PHP 5.4, PHP 5.3, or PHP 5.2 compatible, it might encourage contributors to test them, and make them so.
PHP 5.3 Bad News
I just upgraded to php 5.3 and my drupal 6 sites seemed to work except for the post in my forum. They all show as page not found. Not sure if this is an forum, Advanced Forum, Clean URL, or one of the other many modules that are involved and not sure of any way to figure it out. I sure hate to run two servers since I now have a project that requires 5.3....oh what to do. I sure hope that there is some php comparability tag in the future.
John Williams
Freestone Products
john@freestoneproducts.com
720-560-1460
More Info
I upgraded to php 5.3 again and resolved the issue I was having in the error.log but I am still having one issue I cant resolve. On my site any page that is www.site.com/content/* were * is anything for the rest of the URL comes up with page not found. All other pages are fine. I have been trying to remove modules like pathauto, path etc and closely looked at the .htaccess but I can find now reason why just /content pages are coming up 404? Any help would be appriciated.
John Williams
Freestone Products
john@freestoneproducts.com
720-560-1460
Some things that come into
Some things that come into mind on an early Sunday monring (and you may have tried all of those already)
Set a breakpoint on
function drupal_not_found() in /includes/common.inc and check the stacktrace to see what code causes the 404.
Or very rudimentary if you don't use a debugger, then temporatily change the function to print out where it comes from and have a look at the callers context.
function drupal_not_found() {
drupal_set_header('HTTP/1.1 404 Not Found');
print_r(debug_backtrace());
exit;
The other ideas below would be if you have the same issues with PHP 5.2, but reading your post, I can only assume your site works fine with 5.2. Nevertheless, it might be worth a shot:
Do you access any www.site.com/content/* as anonymous or as a logged in user and you experience the same behaviour?
Can you check your database if you have a user uid==0? If I remember correctly User 0 is required to access content that has been created with uid==0. (But this should be the same with PHP 5.2)
And the most obvious ones:
I take it you have rebuilt the permissions and the menus.
Panel Disabled
Thanks for the info. I tried the buildpermission but id did not work. Then I found that the panel Node_view was disabled for that page. I dont understand this as the page should not have been displayed in php 5.2 and yet it was displaying just fine. I cant image how recompiling with php 5.3 would change that setting. At any rate I can see the page now but it is formated differently. I now have to look at the view involved and figure out why comments is no longer active on that page. What a strange issue this is.
John Williams
Freestone Products
john@freestoneproducts.com
720-560-1460
And now PHP 5.4
The end of life cycle is coming up in March. Already some of my clients are wondering what to do about D6. I'm wondering what to do about D6 & D7 modules as well.
I'm trying to find a list of modules already 5.4 compatible, or more importantly, not compatible. Any progress on tagging modules?
PHP 5.3 Reaching End of Life; PHP 5.5 available
"PHP 5.3.27... will be the last regular release of the PHP 5.3 series. All users of PHP are encouraged to upgrade to PHP 5.4 or PHP 5.5. The PHP 5.3 series will receive only security fixes for the next year." (2013-Jul-11)
Looks like there may be more trouble for folks still migrating up while maintaining stability.
Chris Charlton, Author & Drupal Community Leader, Enterprise Level Consultant
I teach you how to build Drupal Themes http://tinyurl.com/theme-drupal and provide add-on software at http://xtnd.us
PHP y drupal
hola buen dia estoy realizando un desarrollo web en drupal con SQL server y quiero arrojasr los resultados en una pantalla de drupal con codigo PHP pero n o me regresa nada me podrian ayudar