TYPO3 Core

Hi Christopher,

you are absolutely right. Luckily it is only a non public testing environment.
To me the confusing fact is, that this issue did not rise in version prior to TYPO3 4.5.0.

In TYPO3 4.4.X the EM was located in a different path, but it also holds the line:

require('conf.php');

which never caused any trouble. Neither did any other extension cause any problems and I am sure they have relative inclusions as well.

But I see the point that it most likely will be a local problem only that has to be fixed locally and should not be fixed within TYPO3.

The Extension Manager was rewritten for TYPO3 4.5, but anyway that this does not happen anywhere else is an interesting fact...

Could you solve it by fixing the include_path in php.ini?

These are the "include_path" settings from phpinfo() within the TYPO3-Install-Tool:

Local Value:
.:/usr/share/psa-horde/pear:/usr/share/psa-horde/config:/etc/psa-horde/horde

Master Value:
.:/usr/share/psa-horde/pear:/usr/share/psa-horde/config:/etc/psa-horde/horde

Actually it is supposed to look in the current folder first. I did not change this setting, so .. no, the include_path seems to be ok to me and it does not fix the problem. But on the other hand I did not encounter this issue on other servers so far.

The phpinfo also shows these details on the PHP version used:
CONST: php_sapi_name : cgi-fcgi
OTHER: PHP_VERSION : 5.2.0-8+etch16
Server API : CGI/FastCGI

Hmm, what is the current working directory?

I did some debugging and I think I got the issue straight. Probably results in a TYPO3 security issue though.

I added these lines to the file: typo3/sysext/em/classes/index.php
echo getcwd();
exit;

it outputs this path:
/var/www/vhosts/<domain>/httpdocs/typo3_src-4.5.4/typo3

now that explains why it does not find the conf.php file instantly. But it does not explain why the path is set incorrectly or why it results in a problem on my system. Now the answer is within the PHP documentation: http://ca.php.net/manual/en/function.include.php
The problem is, the path is wrong on all TYPO3 installations, but it still works, because there is no conf.php file found within the php include_path, normally. So the least action php does to try to find a conf.php file is this:
--- FROM PHP DOCUMENTATION start ---
If the file isn't found in the include_path, include() will finally check in the calling script's own directory and the current working directory before failing.
--- FROM PHP DOCUMENTATION stop ---

I also figured that the file: typo3/sysext/em/classes/index.php
is required on line 51 in file: typo3/mod.php

I took a look at that file and the difference between the em-extension and the other extensions at the "Admin tools"-Section is, that only the em-extension seems to explicitely require its own conf.php file.

Now my naive question is, why does the em-extension explicitely require its own conf.php file, if it already is required on line 49 in file: typo3/mod.php

I am sure there is a good reason for doing so, but removing these lines:
unset($MCONF);
require('conf.php');

from file: typo3/sysext/em/classes/index.php
also results in a smooth executing.