500 server error at admin/logs/status

Sorry, I have no idea what could cause a 500 server error with filefield, nor have I encountered such a situation yet. In any case, 500 server error could be *anything*, so you'd better look up in your server log what the actual error is. Perhaps that can guide you towards a solution. (Changing to "needs more info" until the exact error is being posted here, as nobody will be able to help otherwise.)

no clues... with 2.3-rc4? have you tried the 2.3 release?

how is your filefield configured? What additional modules are you using with filefield? are there errors in your watchdog? do you have any debugging information to share at all?

did you get a specific error in the apache error logs? How did you discern that mime detect was failing?

Hello!
I've got 500 error at provider's server too.

It using suPHP, so maybe problem is there.
Im installing fresh drupal instance, and its enough to install mimedetect module to get 500 error at admin/logs/status!

Any ideas where i should go?)

Update:
If im using drupal localization language - problem persist. When i swithing off all localizations (except english one) - i've got no 500 error at all! Nowhere!

Hi,

I was having the same problem and tracked it down to the following line:

    if ($finfo || $finfo = @finfo_open(FILEINFO_MIME, drupal_get_path('module', 'mimedetect') .'/magic')) {
        $mime = finfo_file($finfo, $file->filepath);
    }

If you remove the path to the custom 'magic' file then it will revert to the default magic path - 'mime_magic.magicfile' set in php.ini.

This may well solve your problem - it was the custom magic file that was throwing an error on the production server (although everything was working fine locally).

I don't know too much about how to debug the magic database itself...

This is the alternative code:

    if ($finfo || $finfo = @finfo_open(FILEINFO_MIME)) {
        $mime = finfo_file($finfo, $file->filepath);
    }

Obviously it would be better to fix the bug in the magic file - it was causing a segmentation fault on my production server.

Cheers!

Thank you featherbelly, I finally managed to activate mimedetect module correctly (in Drupal 6) with your help...
I also received "Segmentation fault" all the time...

Well, to help people avoiding hours to loose, here is my working procedure:

- first search in your system where the default magic file is located, mine was here /usr/share/misc/magic (OpenSUSE 10.2)
- de-activate mimedetect module if it is not the case already
- uninstall the module (?q=admin/build/modules/uninstall) - this is important
- edit mimedetect.install file, and replace:
if (!$finfo = @finfo_open(FILEINFO_MIME, drupal_get_path('module', 'mimedetect') .'/magic')) {
with:
if (!$finfo = @finfo_open(FILEINFO_MIME, '/usr/share/misc/magic')) {
- edit mimedetect.module file, and replace:
$magic_file = drupal_get_path('module', 'mimedetect') .'/magic';
with:
$magic_file = '/usr/share/misc/magic';
- re-activate the module, and now it works!

;-)

I wonder, if one looks inside the MimeDetect module readme.txt if they might find the instructions to add the 'magic' file location to the config.php?

Just a thought before attempting the #14 response. If I used the #14 method then I would be required to redo the config changes every time the module changes, that might be a pain.....

Using the config settings for the location of the magic file would prevent having to make the change to the module as described in #14.

clement006 Nice work figuring out another method for sorting out this issue!

Assumed fixed. If not, please, reopen it.