Posted by bbeyer on August 13, 2008 at 4:47pm
Jump to:
| Project: | FileField |
| Version: | 6.x-3.x-dev |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
http://drupal.org/project/filefield says that PHP5 is required but 5.2 is recommended. But when I attempt to enable the module it tells me that it can't because 5.2 is required. Is that going to be the case going forward? If so, the documentation should be updated. Also, out of curiosity, what in the module requires PHP 5.2?
Comments
#1
fixed the project page to list PHP 5.2 as the minimum.
#2
What is in the module that requires PHP 5.2? I am wondering if I could customize it for myself to make it work with 5.1
#3
Are you aware that Drupal 7 will require a minimum of PHP 5.2.5? Stop worrying and get your hosts upgraded.
#4
@bbeyer: It requires 5.2 because I use 5.2. I keep finding bugs on 5.1 hosts I cannot reproduce on 5.2. I choose to only support PHP >= 5.2. You can figure out the nuances of the bugs fixed between 5.1 and 5.2 if you really need to run on 5.1 or you can just try using 5.1 but that is unsupported.
#5
So. Is there any way to enable this modul on php 5.1. Because I have php 5.1.2 and Drupal says that modul isn't supported. The note on the right is "This module requires PHP version 5.2.* and is incompatible with PHP version 5.1.2."
#6
Go to the .info file and change the "PHP" line.
#7
Automatically closed -- issue fixed for two weeks with no activity.
#8
I'm having the same issue. Our host uses CentOS, which thus far does not support anything beyond 5.1.6, and it's proving very difficult to get around that issue at the moment. Were you able to adjust the .info file and get filefield to work? Did you run into any serious bugs? Thanks for any help.
#9
Just remember, you can't even think about D7 until you get to 5.2.5.
#10
Agreed, although I imagine we won't be moving to D7 for at least a year, and by then our host / CentOS should be updated. But in any event, I was able to convince our host to use a dev version of CentOS to upgrade to 5.2.6 just now. The problem seems to be that these host packages are very conservative about their component versioning. CentOS doesn't consider anything beyond 5.1.6 fully tested / stable from their package point of view yet :(
#11
D7 aside, I am seeing more and more contribs requiring 5.2 as well. I'm glad your host saw the light. I've seen a number of RHEL hosts that have been on 5.2.5 and above for some time; I think it's adequately tested.
#12
Yeah, I just saw another important module that required 5.2 last night come to think of it (the date module I believe).