Issue Bug Closed

#109685TYPO3 14 legacy installation (symlink) does not create "ext" directory

Christian Hackl 04/22/26, 11:19 updated 04/23/26, 14:24

Description

TYPO3 14 does not create the directory “typo3conf/ext/” after installation / after extension-list update via ExtensionManager.

TYPO3 14.3.0 – PHP 8.5 – symlink installation with ENV:
- TYPO3_PATH_APP = /httpdocs/myproject/
- TYPO3_PATH_ROOT = /httpsdocs/myproject/public/
- TYPO3_CONTEXT = Development

I installed TYPO3 14.3.0 with the env’s above via symlinks.
I loggedin and updated the extension-list via ExtensionManager (“Get Extensions” option).
Then i tried to install a extension e. g. “news”.
The error-message / hint-message appears: ‘ERROR: The extension install path “typo3conf/ext” was no directory’.

I would assume that TYPO3 creates this default “ext” folder on its own. (The “directory-status” also doesn’t return any error messages.)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Files 2

History 6

  1. Helmut Hummel commented and changed status New Needs Feedback <span data-processor="relativetime" data-value="2026-04-22T12:02:28+00:00" > 04/22/26, 12:02 </span>

    Christian Hackl wrote:

    > – TYPO3_PATH_APP = /httpdocs/myproject
    > – TYPO3_PATH_ROOT = /httpsdocs/myproject/public

    You are running into this, because such setup is not supported. Those variables are not meant to be changed and for sure not meant
    to be set to differ in classic mode.

    If you don’t set those, you are not getting these issues, right?

  2. Christian Hackl commented <span data-processor="relativetime" data-value="2026-04-22T13:10:33+00:00" > 04/22/26, 13:10 </span>

    Hmm, if I’m reading this correctly, it’s supported since TYPO3 9; see:
    https://docs.typo3.org/m/typo3/reference-coreapi/9.5/en-us/ApiOverview/Environment/Index.html#configuring-environment-paths

    I can’t find anything to the contrary, or any indication that it was ever deprecated.

    Even if it weren’t supported, I’d suggest that it be supported, since it definitely improves security—for example, by storing log files outside the DocRoot.

  3. Helmut Hummel commented <span data-processor="relativetime" data-value="2026-04-23T14:22:27+00:00" > 04/23/26, 14:22 </span>

    Hm, you are right, that this has been documented back then. Unfortunately this
    was never really enforced or communicated well, so that new code that was added diverged.

    Good news however is, that a setup in “classic” mode where everything besides
    public assets being outside document root
    is very close.

    With #109470 being part of 14LTS, there are only a few things missing to allow that

  4. Helmut Hummel commented and changed status Needs Feedback Closed <span data-processor="relativetime" data-value="2026-04-23T14:24:42+00:00" > 04/23/26, 14:24 </span>

    I close this as duplicate