Closed (fixed)
Project:
FileField
Version:
6.x-3.7
Component:
Code
Priority:
Minor
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
2 Sep 2010 at 08:38 UTC
Updated:
17 Sep 2010 at 14:00 UTC
Hi, not sure whether this is a bug or something else...
The progress bar seems to be working fine. However, I still get this message when running cron:
Your server is not capable of displaying file upload progress. File upload progress requires PHP be run with mod_php and not as FastCGI.
The site is hosted with www.bluehost.com, and in PHP configuration I have single.phi activated, not fastcgi.
Comments
Comment #1
quicksketchWhat is "single.phi"? This error probably shows up every time you visit admin/reports/status, rather than being specific to Cron.
FileField attempts to figure out if your server is running PHP as FastCGI by checking the $_SERVER['SERVER_SOFTWARE'] global. However it's not 100% accurate. What's the value of SERVER_SOFTWARE for you? You can check by visiting admin/reports/status/php.
Here's the line that determines if you're running FastCGI or not:
Comment #2
LarsKramer commentedSingle phi just means that the php.ini in the root folder is used for all sites on my account.
I already took a look at that code line. However, I don't know sufficient PHP/Apache to understand what it means.
The value of SERVER_SOFTWARE is:
Apache/2.2.16 (CentOS) mod_ssl/2.2.16 0.9.8l DAV/2 mod_fcgid/2.3.5 mod_auth_passthrough/2.1 FrontPage/5.0.2.2635Comment #3
quicksketchSo according to your server string, FastCGI is running as indicated by the
mod_fcgidpart. However, this doesn't necessarily mean that FastCGI is being used for PHP (it's just very likely). Like I said FileField does its best to guess if you're running PHP as mod_php (a native Apache extension) or as FastCGI. Given your server string, I think it made a likely guess. I certainly would expect PHP to be running as FastCGI given that same information. I'm not sure that there's much to be done, a false warning is better than saying that upload progress should work fine when it doesn't.Comment #4
LarsKramer commentedGot this answer from Bluehost support:
Feel free to close the issue. It seems there is no way to solve it. Thanks for your time
Comment #5
quicksketch