Use other file MIME detection instead of the mime.types file

I think you're getting this error because your php is run in a safe mode http://lt.php.net/manual/en/features.safe-mode.php

Try entering the location of the MIME file in the file settings page.

I am having the same error and am pretty sure safe_mode is set to OFF.

I began to get this error after I moved the site from one server to another. Mirrored every single settings (I think). But something is missing obviously.

Any updates on this issue? Thanks,

Drupal 6.10
File Framework 6.x-1.0-alpha3
Bitcache 6.x-1.0-beta1
Resource Description Framework (RDF) 6.x-1.0-alpha6

Does mime.types file have a read permissions for the user running the web server?

That's what I am told. It's a dedicated-virtual box. Currently root access is not enabled (it is optional). But I was told I have read access to that file.

I entered the path "/etc" to Path to the server's MIME type definitions 'mime.types' file field at http://domain.com/admin/settings/file

Even the Server-side MIME type autodetection after upload option is set to Disabled I get this error message:

warning: file_exists() [function.file-exists]: open_basedir restriction in effect. File(/etc/mime.types) is not within the allowed path(s): (/var/www/vhosts/domain.com/httpdocs:/tmp) in /var/www/vhosts/domain.com/httpdocs/sites/all/modules/fileframework/file.admin.inc on line 188.
A file /etc/mime.types does not exists or is not readable by the web server.

So, does it mean I do not really have read access to mime.types or there's another issue?

Thanks,

This should be simple to fix. As the error says, there is an open_basedir restriction in effect which prevents Drupal from opening the mime.types file. All you need to do is get a copy of an Apache mime.types file (it's included in most Unix operating systems, including Mac OS X; you could also Google for it), and put it somewhere under your Drupal directory where File Framework can access it.

@Miglius, I suggest we ship a decent mime.types file with File Framework. The ones included with operating system distros tend to be out of date, anyway. Take a look at file_get_mimetype() in core's includes/file.inc; if nothing else, that would be easy to turn into mime.types format and ship as default.

Hi Arto,

Thanks for the quick reply. It works without error now.

Cheers,

Agree that we cannot assume that mime.types file is recent. I'm leaning of using file_get_mimetype() as the base for the mime types, giving the possibility for the format* modules to add mime types programaticaly and also adding configuration option for adding new or overwriting existing mime types at the settings pages.

Thanks Miglius. Thanks Arto.

Miglius, do you foresee this coming out in a release soon or do you have an idea of when it would take place?

(I admit I don't know the code or possible rework involved to handle it... I'm just curious as to if you have it mapped out or planned for an upcoming release)

I plan to implement it and commit to cvs by the end of this week so it will be available in the development release. Not sure when a new alpha will be cut though.

Thanks for the update, Miglius. I'll have to check it out once things slow down, work-wise.

I have committed the changes. The new code gives more documentation how the MIME detections is performed. Also it abandons dependence on the mime.types file. The system uses the MIME definitions given by the core drupal file.inc file. It's a pity I can not reuse the same file but have to replicate it though...

Also now a new MIME types can be added or existing types overwritten in the configuration area.

Please, test it.

Automatically closed -- issue fixed for 2 weeks with no activity.