Hello,

There were several topics on Drupal 6.x general incompatibilities with PHP 5.3. I don't talk about clean installation, I talk of real-life sites with many modules enabled.

However, PHP.net has announced the end-of-life for PHP 5.2. I admit that not all module developers do care about PHP.net announcements, but perhaps it's time to propose a PHP version compatibility attribute for modules listed at Drupal.org?

It could save a lot of time in the very near future. If you are using your own server, you can compile whatever PHP you need, knowing the risks. IF you use third-party hosting, you are not that free in your choice.

So, whom shall I contact to draw serious attention to the PHP version change problem?

Thanks.

Comments

Vasu’s picture

I too agree with that. Since there are quite a lot of production sites running with Drupal 6x contributed modules which are not ready for php 5.3 it is a serious problem for users running sites on shared hosting.

Vasu’s picture

There is a group for PHP, but doesn't look very promising.
http://groups.drupal.org/php

Chris Charlton’s picture

I setup the PHP group to help people get info on stuff like this. There's been only a flood of job posts, so I'll work to move those into their own tab or column to allow the real discussions and posts to not get buried.

Chris Charlton
Manager
LA Drupal
Drupal Author
Published since 2007
pcoughlin’s picture

The points raised here are good ones. Adding the "PHP version attribute" would at least warn people of the potential for problems.

Good idea.

Chris Charlton’s picture

Here's a link to the documentation. As you'll see the PHP version is a requirement attribute. http://drupal.org/node/231036

Also, hook_requirements() can easily detect PHP version and stop a module from being installed if the server software isn't supported.

Chris Charlton
Manager
LA Drupal
Drupal Author
Published since 2007
marcelgalema’s picture

I'm already getting questions about this... with the focus now on D7 this might kick us in the back sooner than we like :-(

thomasmurphy’s picture

I think this is quite a core issue. I'm just starting a large drupal project and am choosing to start it in Drupal 6 because of 3rd party module availability, the number of sites running 6 rather than 7 and the number of local drupal shops with a sucessful track record in 7, which is, unsurprisingly, low at present. We need some kind of way of listing 6.x modules which have PHP 5.3 compatability issues. Can we post them all here, or does this exist already? Alternatively, what do people think about running PHP 5.2.x long term, despite it being "unsupported"...?

Konstantin Boyandin’s picture

A good idea, post the list of modules not supporting 5.3.* branch of PHP.
I can only suggest contacting module developers and asking about the compatibility issues (I expect we would need at least 4 typical responses: '5.2 only', '5.2 and 5.3', 'Don't care' and no response from module maintainer at all).

I can start asking ASAP and post the responses here. I think Drupal core developers should also be asked about this. Thanks.

Chris Charlton’s picture

PHP.net has a guide for PHP developers on how to migrate from PHP 5.2 to 5.3, here's the link: http://php.net/migration53

For quick details, here's a list of the deprecated functions in PHP 5.3 - http://us3.php.net/manual/en/migration53.deprecated.php

Chris Charlton
Manager
LA Drupal
Drupal Author
Published since 2007