Drupal crashes with a white screen (i.e., nothing returned) after enabling Media Mover module.

No log entries.

Any suggestions for possible causes / workarounds?

Comments

escoles’s picture

escoles commented

Additional info:

Same behavior when installing 5.x-1.0-alpha1.

This is the error reported in the PHP log:

PHP Parse error: syntax error, unexpected '=', expecting ')' in /Users/escoles/Sites/turnerproto/modules/media_mover/media_mover_api.module on line 426

PHP version is 4. Is Media Mover PHP 5-only? For now, PHP 5 is not an option.

escoles’s picture

escoles commented

It looks as though Media Mover may be de facto PHP5-only:

http://drupal.org/node/186744

Can you verify and if so change the module description to include that information?

arthurf’s picture

arthurf commented

can you check your logs and see if there are any errors for missing functions?

escoles’s picture

escoles commented

Error I cited was the only error logged for that time.

I looked at the code around the line referenced, and it's all correct as far as I could tell. Anyway, if it were a problem with the code per se, you'd have seen a lot more errors than this. It's plausible to me that you haven't had an install on PHP 4.4.7 since your last updates.

I'll try to find some time to test against PHP5 and post results.

escoles’s picture

escoles commented
Title: White Screen after enabling Media Mover » PHP 4 Incompatability [was: White Screen after enabling Media Mover]

I've verified that Media Mover will install under PHP 5, but not under PHP 4.4 or 4.7. Changing Issue Title to reflect real issue.

arthurf’s picture

arthurf commented

I'd be happy to accept patches to make it compatible with php4, but for right now, the push is to make things stable and usable for drupal con in hungary.

escoles’s picture

escoles commented

For now, would it be possible to change module page to mention that there appears to be a PHP4 compatability issue? It's kind of a big deal AFAIAC, but maybe not for a reason that would be obvious to you, and that's that Asset does not have such an issue. Counter-intuitive, but here's my logic: If you try to deploy an asset management solution with Asset alone, you're setting yourself up for some really horky user interaction issues (since Asset doesn't play well with IMCE -- can't upload into directories created by Asset, e.g. -- and you effectively need IMCE or something like it to have WYSIWYG "asset" insertion).

(I just went through the process of designing an elegant solution using Asset that I had to dump at the literal 11th hour -- re-coded/re-integrated the solution one hour before trainign on it -- because of the user interaction issues. So I'm a little sensitive to it. There are a surprising number of servers out there still not running on PHP5.)

Mind you, I really like Asset and I'll probably like Media Mover, but IMO and AFAICS, they really shouldn't be deployed separately -- doing so sets you up for significant usability issues in exactly the user community that one would be targeting with solutions based on these modules.

arthurf’s picture

arthurf commented

Actually, the project page does mention that it doesn't run on php4, but I do think that it's possible that we could bridge this- the issue seems to be that in the hook_media_mover(... &$file = array() which is fine in php5, but deadly in php4. Basically it means rewriting the hook calls inside media_mover_api to populate $file with array() when it's null and removing this assignment from the hook. I'd be happy to take a patch if one was offered :)

arthurf’s picture

arthurf commented
Status: Active » Closed (fixed)

I don't think back port to php4 would be hard, I just need to know if it is wanted. Closing until I hear otherwise.