TYPO3 Core

After an update from 4.5.25 to 4.5.26 the same problem exists.

PHP version used on one dev/test server is 5.2.5.

Borries Jensen wrote:

After an update from 4.5.25 to 4.5.26 the same problem.

PHP Version used on one Dev/Test-Server is 5.2.5

Thanks for your response. What distribution/operating system and which version are you using?
Is it a custom compiled PHP version or a standard package of PHP that is being used?

Ok, detailed info of the dev machine follows:

SUSE Linux Enterprise Server 10 (i586)
VERSION = 10
PATCHLEVEL = 2

PHP 5.2.5 with Suhosin-Patch 0.9.6.2 (cli)
This PHP version is/was the one from SLES repository (no custom compilation done by us).

What's going on here??
mime_content_type is available since PHP 4.3, so the method should be present in 5.2.5.

Hm, am i right that to use the function mime_content_type() the server needs not only the apache module "mod_mime" but also "mod_mime_magic" ?

I just checked the server which causes the mentioned error.
Only "mod_mime" is active there.
Maybe that's causing the error.

According to http://php.net/manual/en/fileinfo.installation.php the Fileinfo extension requires a (patched) magic_open library (libmagic) in PHP versions < 5.3.0. It is provided and enabled by default, but still not part of the PHP core.
As of PHP 5.3.0 (?) mime_content_type() is deprecated and replaced by the finfo class.

All in all: these functions/classes seem to be moving ground and might require a more sophisticated approach. I think a wrapper method to abstract from the different implementations should help.

There's another requirement that might play a role: required library "magic_open"
http://at1.php.net/manual/en/fileinfo.requirements.php

Only enabling "mod_mime_magic" did not solve the problem.
Just tried it on the mentioned machine.

It's a regression thus needs to be fixed. Not having a mime-type for the favicon does not harm (as it has been before), but running into a fatal error on each frontend request does. No need to discuss that further - it's a bug.

I guess a simple function_exists() call to check the existence is fine?

Hi,

Will these result in a new TYPO3 release? Or just included in next release? I have a lot of solutions not updated cause of the issue.

@Tomas: It will definitely be included in the next bugfix release. In the meanwhile you can apply the patch manually to your installations.

@Markus: Do you know when next release will be? Have about 15 servers which need to be patched. And normally I/we don't allow "manipulated" sources.