[TYPO3-dev] Bug? 4.0.2: yes. 4.0.4: NO! with intermediate folder 'ssl'

[Martin Bless]

Something odd.

When I change the symlink ./typo3_src from ../typo3_src-4.0.2 to
../typo3_src-4.0.4 I get just a single line of output:

"""Error: The main frontend extension "cms" was not loaded. Enable it
in the extension manager in the backend."""

This only happens with the url https://mydomain.de/ssl/cms. It's the
same one that works with no problem with 4.0.2.

I renamed the intermediate folder ./ssl/ to ./abc/ and the problem
vanishes. My conclusion: In v4.0.4 the name 'ssl' of the folder causes
a problem - which it really shouldn't. A bug?

Yes, I had a look at the bugtracker but wasn't sure where to put this
odd thing.


Here's some of my protocol to track the error:
(debian linux, with pseudo linenumbers)

case 1:

101  /var/www/user/html/cms/typo3_src -> ../typo3_src-4.0.2
102  /var/www/user/html/cms/typo3     -> typo3_src/typo3
103  /var/www/user/html/cms/t3lib     -> typo3_src/t3lib
104  /var/www/user/html/cms/index.php -> typo3_src/index.php
105  /var/www/user/html/abc/cms -> ../cms
106  /var/www/user/html/ssl/cms -> ../cms
107
108  https://mydomain.de/cms/        <-- ok, no problem
109  https://mydomain.de/abc/cms/    <-- ok, no problem
110  https://mydomain.de/ssl/cms/    <-- ok, no problem

case 2:

201  /var/www/user/html/cms/typo3_src -> ../typo3_src-4.0.4
[...]
208  https://mydomain.de/cms/        <-- ok, no problem
209  https://mydomain.de/abc/cms/    <-- ok, no problem
210  https://mydomain.de/ssl/cms/    <-- NOT ok, PROBLEM!

With line 201 I get as a result from 210 this single error line:

"""Error: The main frontend extension "cms" was not loaded. Enable it
in the extension manager in the backend."""

As I sad, renaming the folder 'ssl' in 210 to 'somethingelse' helps.

Anyone?

Have a nice day

Martin