#109825TYPO3 14.3.1 update BREAKING - ERROR: [TYPO3_PATH_APP]/packages/sysext/*/" directory does not exist.
Description
Classic installation (symlinks)
Update from 14.3.0 to 14.3.1 not possible, after changing the symlinks the error appears:
The "D:/typo3-test-version/typo3-14.localhost/packages/sysext/*/" directory does not exist.
Completely new installation, new directory fresh new symlinks the same error appears instantly.
Clear / delete cache manually – no change.
Server restart – no change.
Set the symlinks back to 14.3.0 – clear cache – works again.
PHP 8.5
env TYPO3_CONTEXT=Development/Server
env TYPO3_PATH_APP=D:/typo3-test-version/typo3-14.localhost
env TYPO3_PATH_ROOT=D:/typo3-test-version/typo3-14.localhost/public
Perhaps related to:
https://github.com/typo3/typo3/commit/770c5383930
https://forge.typo3.org/issues/109685#change-568598
https://forge.typo3.org/issues/109686#change-568607
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch
- Commit message
-
[BUGFIX] TYPO3 14.3.1 update BREAKING - ERROR: [TYPO3_PATH_APP]/packages/sysext/*/" directory does not exist. Resolves: #109825 Releases: main
Files 5
History 17
-
Christian Hackl commented and changed attached typo3-14.3.1-directories.JPG attached error-14.3.1.JPG <span data-processor="relativetime" data-value="2026-05-12T14:25:02+00:00" > 05/12/26, 14:25 </span>
-
Garvin Hicking commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2026-05-12T16:25:23+00:00" > 05/12/26, 16:25 </span>Please copy the full stacktrace as text, you can use thecnew cooy to clipboard feature. Thanks.
-
Helmut Hummel commented <span data-processor="relativetime" data-value="2026-05-12T16:44:10+00:00" > 05/12/26, 16:44 </span>
Christian Hackl wrote:
> env TYPO3_CONTEXT=Development/Server
> env TYPO3_PATH_APP=D:/typo3-test-version/typo3-14.localhost
> env TYPO3_PATH_ROOT=D:/typo3-test-version/typo3-14.localhost/publicI tried to point out for you in
#109685 and #109686 already, that such setup wasn’t really supported, despite documented in a single feature rst for typo3 9.5There were many places in the code, that
broke this “feature” long after it was announced.At the same time, the changes done for 14.3.1
fixed all those places and also aligned all paths to match the paths of a Composer based installation.Also note that there’s no breaking change for classic mode, when path env vars are not changed.
I’m sorry this now causes some troubles for you. I invite you though to either switch back to not changing the env vars at all and stick with pure classic mode, or to test out going all in with the new directory structure.
The latter provides an even more secure setup, which you wanted to achieve if I understood you correctly.
If you are willing to do those extra steps, let me know and I will add as much information what is required for that here (and in the docs later).
-
Christian Hackl commented and changed attached stacktrace-full.txt attached stacktrace.txt attached logs.txt <span data-processor="relativetime" data-value="2026-05-13T08:09:44+00:00" > 05/13/26, 08:09 </span>
Thank you both for the feedback and the explanation.
Before anything else: I will provide the full stack trace as requested (files).
That said, I’d like to address a few points:
**Regarding the documentation:**
This feature was not only documented in a single RST file. I can point to at least three changelog entries as well as the inline comments in `Environment.php` itself (found within TYPO3 13 LTS):
- `typo3/sysext/core/Documentation/Changelog/9.2/Feature-84153-IntroduceAGenericEnvironmentClass.rst`
- `typo3/sysext/core/Documentation/Changelog/9.2/Feature-84545-AllowTemporaryFilesToBeStoredOutsideTheDocumentRoot.rst`
- `typo3/sysext/core/Documentation/Changelog/9.4/Feature-85256-InstallTYPO3OnSQLite.rst`
- `typo3/sysext/core/Classes/Core/Environment.php` (inline comments)**Regarding the breaking change classification:**
We have been using this setup across well over 100 production installations reliably across multiple TYPO3 versions, without any issues. Regardless of whether the original implementation fully anticipated Classic Mode usage, removing documented and working behavior in a minor update (14.3.0 → 14.3.1) is a breaking change by any standard definition. I would kindly ask that this be acknowledged as such, and that a proper migration path or deprecation notice be provided — ideally tied to a major release.The statement “there is no breaking change when path env vars are not changed” is technically true, but it effectively means: users who relied on a documented feature are now broken. That is the definition of a breaking change.
**Regarding Composer:**
Not every deployment scenario makes Composer on production systems feasible or desirable. In many of our cases, server access is limited to FTP — Composer is simply not an option. Classic Mode exists precisely for these real-world use cases, and I’d strongly caution against implicitly pushing users toward Composer-based setups without a clear, documented migration path for those who cannot use it. -
Helmut Hummel commented <span data-processor="relativetime" data-value="2026-05-13T08:59:20+00:00" > 05/13/26, 08:59 </span>
Christian Hackl wrote in #note-4:
> **Regarding the documentation:**
> This feature was not only documented in a single RST file. I can point to at least three changelog entries as well as the inline comments in `Environment.php` itself (found within TYPO3 13 LTS):True. I wasn’t aware of that and, judging from some places in the code, others within the team either. Again I’m sorry about that.
> removing documented and working behavior in a minor update (14.3.0 → 14.3.1) is a breaking change by any standard definition. I would kindly ask that this be acknowledged as such
I fully agree and it is undeniably a breaking change for the described scenario.
> We have been using this setup across well over 100 production installations reliably across multiple TYPO3 versions, without any issues.
You are having 100+ production installations with TYPO3 14.3.0?
> and that a proper migration path or deprecation notice be provided — ideally tied to a major release.
We have multiple options:
1. Roll back, make everything work in classic mode like it worked in v13 with changed TYPO3_PATH_APP and at the same time deprecate this setup
2. Provide full documentation and migration to the new directory structure, that puts not only a few, but all private files into private directories and exposes only truly public files in the public directory. A more secure setup that was previously only possible using Composer, would be now possible with TYPO3 v14 already (it currently actually is, yet documentation and migration path is missing)If we choose for 1. then you could use the setup you previously used also for v14, but will have to change it for v15
If we choose 2. you will have more work now when now migrating to v14, but will benefit from a more secure setup.I (obviously?) recommend option 2. Although it came quite late and causes trouble that you thankfully pointed out, I think it also holdes the most benefits.
What would you personally prefer?
> **Regarding Composer:**
> Not every deployment scenario makes Composer on production systems feasible or desirable. In many of our cases, server access is limited to FTP — Composer is simply not an option. Classic Mode exists precisely for these real-world use cases, and I’d strongly caution against implicitly pushing users toward Composer-based setups without a clear, documented migration path for those who cannot use it.Thanks for your input here. I was not talking about requiring Composer based setups, but wanted to advertise the directory structure, that is possible with Composer based TYPO3 setups since TYPO3 v12, but was not possible before in non Composer setups. Non Composer TYPO3 setups deserve the same level of security is what I wanted to point out.
-
Helmut Hummel changed priority
Should haveMust have target version <span data-processor="relativetime" data-value="2026-05-13T09:00:02+00:00" > 05/13/26, 09:00 </span> -
Christian Hackl commented and changed priority
Must haveShould have target version <span data-processor="relativetime" data-value="2026-05-13T11:32:07+00:00" > 05/13/26, 11:32 </span>Thank you for the clarification and for acknowledging this as a breaking change — that is appreciated.
**Regarding the 100+ installations:**
To clarify: these are currently running on TYPO3 v13 (and older). Upgrading them to v14 would require touching every single one of them — and with the current situation, that would mean a significant rework of each installation’s directory structure (and current deployment workflow). That is the scale of impact we are talking about (for us – i don’t know how many other people uses classic-mode with this env’s too).**Regarding Option 1 vs. Option 2:**
I would strongly prefer Option 1. Here is why:Option 2 sounds beneficial in theory, but it assumes that all Classic Mode users have the infrastructure to perform a significant directory restructuring — with proper deployment pipelines, shell access, and the ability to test thoroughly. In reality, many Classic Mode installations exist precisely because those tools are not available. In some of our cases, access is limited to FTP only. For those scenarios, Option 2 is simply not feasible.
I would also like to point out that keeping TYPO3_PATH_APP and TYPO3_PATH_ROOT functional in Classic Mode does not prevent a more secure directory structure — it enables it. Removing these variables takes away the ability to configure Classic Mode more securely, which seems contrary to the stated goal of bringing Classic Mode to the same (more or less) security level as Composer-based setups.
Option 1 — roll back, restore the previous behavior, and deprecate with proper notice for v15 — is the approach that respects existing users, gives time for a proper migration, and does not force an all-or-nothing decision on (maybe) thousands of installations worldwide. I think this should be the normal steps for breaking changes.
But:
Helmut Hummel wrote in #note-5:
> A more secure setup that was previously only possible using composer, would be now possible with TYPO3 v14 already (it currently actually is, yet documentation and migration path is missing)Could you please explain that statement in a bit more detail? I’m not entirely sure what exactly you mean. Are you saying that I can use classic mode with TYPO3 14.3.1 and the new structure — in my case like:
“D:/typo3-test-version/typo3-14.localhost/packages/sysext/“
“D:/typo3-test-version/typo3-14.localhost/public/index.php“
“D:/typo3-test-version/typo3-14.localhost/public/fileadmin/“
“D:/typo3-test-version/typo3-14.localhost/var/“
“D:/typo3-test-version/typo3-14.localhost/config/”— without Composer? Without shell access? (In the respective scenarios using FTP only, the environment variables are set via .htaccess.)
I would be perfectly happy with that, or rather, I would have no problem implementing those changes right now, even though breaking changes shouldn’t really be made within an LTS release.Maybe we’re talking past each other a bit here :)
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2026-05-13T15:18:08+00:00" > 05/13/26, 15:18 </span>
Just a sidenote from the audience: You can easily use composer locally and upload the resulting priject via FTP.
You can use such a setup in full composer mode without having shell access, only with FTP. So in a way you’re utilizing a “safe composer-mode directory structure” in classic mode with envs as a workaround, which could be done all with a composer-based deployment techniqu, even giving you a much easier local development framework and easier updates locally. So that’s maybe also worth thinking about?
-
Christian Hackl commented <span data-processor="relativetime" data-value="2026-05-19T14:39:09+00:00" > 05/19/26, 14:39 </span>
Thanks for the suggestion, Garvin. You are right that Composer can be used locally and deployed via FTP, that is a valid workflow for some scenarios.
However, I’d like to keep the focus on the actual issue here: a documented feature was removed in a minor update without a deprecation notice. Whether alternative workflows exist does not change that fact, and I wouldn’t want that point to get lost in the discussion. :) -
Garvin Hicking commented <span data-processor="relativetime" data-value="2026-05-19T15:27:28+00:00" > 05/19/26, 15:27 </span>
Sure! I’m just trying to see a way forward. What di you say to Helmuts auggestion?
I think we should document and provide a “proper” solution now and not reinstate a solution that will hinder progress for the next 3 years of the LTS support there.
-
Helmut Hummel commented <span data-processor="relativetime" data-value="2026-05-28T10:12:30+00:00" > 05/28/26, 10:12 </span>
Christian Hackl wrote in #note-7:
> Could you please explain that statement in a bit more detail? I’m not entirely sure what exactly you mean. Are you saying that I can use classic mode with TYPO3 14.3.1 and the new structure — in my case like:
>
> “D:/typo3-test-version/typo3-14.localhost/packages/sysext/“
> “D:/typo3-test-version/typo3-14.localhost/public/index.php“
> “D:/typo3-test-version/typo3-14.localhost/public/fileadmin/“
> “D:/typo3-test-version/typo3-14.localhost/var/“
> “D:/typo3-test-version/typo3-14.localhost/config/”Yes, exactly!
> — without Composer? Without shell access? (In the respective scenarios using FTP only, the environment variables are set via .htaccess.)
Yes!
> I would be perfectly happy with that, or rather, I would have no problem implementing those changes right now
Great to hear! This would be option 2 then.
> even though breaking changes shouldn’t really be made within an LTS release.
True. Apologies again, that we lost this case from our radar.
> Maybe we’re talking past each other a bit here :)
Seems so :)
-
Christian Hackl commented <span data-processor="relativetime" data-value="2026-06-01T07:40:24+00:00" > 06/01/26, 07:40 </span>
Thank you for the clarification, that is very helpful and good to know!
Could you please provide the concrete steps required to set up this new directory structure in Classic Mode without Composer and without shell access? Specifically:Which environment variables need to be set (and where, e.g. .htaccess)?
What does the expected directory structure look like exactly?
Are there any additional configuration steps required?Once that is documented, I am happy to test it and provide feedback.
-
Martin Hofmann commented <span data-processor="relativetime" data-value="2026-07-02T12:32:00+00:00" > 07/02/26, 12:32 </span>
Hi all,
I’m facing the exact same issue as Christian described above — same error on update to 14.3.1 with TYPO3_PATH_APP / TYPO3_PATH_ROOT set in a Classic Mode setup.
I’d really appreciate it if the concrete steps for the new directory structure (without Composer, without shell access, e.g. via .htaccess) could be documented.
Happy to test any proposed solution as well.
Thanks! -
Martin Hofmann commented <span data-processor="relativetime" data-value="2026-08-03T12:08:36+00:00" > 08/03/26, 12:08 </span>
Just wanted to follow up here — it’s been about three months since this was reported and confirmed as a breaking change, and about a month since the last update (#12). We understand these things take time, but we haven’t seen any documentation yet for the new directory structure without Composer / without shell access that was mentioned as the way forward.
The reason we’re asking is that we have some pending update jobs on production installations that are currently on hold because of this, so we’d really appreciate any guidance on the env vars, .htaccess config, and directory layout mentioned in #12 — even a rough idea of timing would help us plan.
Thanks for the work you’re putting into this, and let us know if there’s anything we can help test once something is ready!
-
Helmut Hummel commented <span data-processor="relativetime" data-value="2026-08-05T12:11:13+00:00" > 08/05/26, 12:11 </span>
Martin Hofmann wrote in #note-14:
> But we haven’t seen any documentation yet for the new directory structure without Composer / without shell access that was mentioned as the way forward.Sorry for the slow response. I
prepared a change to clarify everything, but got lost in a whole lot of other obligations.I will try to at least document what is currently possible here in this ticket as soon as possible
-
Christian Hackl commented <span data-processor="relativetime" data-value="2026-09-16T12:09:44+00:00" > 09/16/26, 12:09 </span>
Just a note: In the current TYPO3 14.3.7 release, the reference to the “TYPO3_PATH_APP” variable is still present:
typo3/sysext/core/Classes/core/Environment.php L:178 -
Christian Hackl commented <span data-processor="relativetime" data-value="2026-10-05T14:19:01+00:00" > 10/05/26, 14:19 </span>
Since I haven’t received a response here, I ran a bot through it — initial tests, including installing via Extension Manager on BE from, for example, EXT:news, worked fine.
I tested the new directory structure (option 2) with a completely fresh TYPO3 14.3.7 Classic Mode installation, without Composer. Installation and backend login work, but I ran into two maybe core bugs(?) that only occur when TYPO3_PATH_APP differs from TYPO3_PATH_ROOT. Both have a simple fix.
Setup used:
SetEnv TYPO3_PATH_APP D:/typo3-test.localhost
SetEnv TYPO3_PATH_ROOT D:/typo3-test.localhost/publicManual steps (cd D:/typo3-test.localhost):
1) curl -L -o typo3_src.zip https://get.typo3.org/14.3.7/zip
2) tar -xf “typo3_src.zip“
3) mkdir public
4) cd public
5) mklink /d typo3_src ../typo3_src-14.3.7
6) mklink index.php typo3_src/index.php
7) echo “” > FIRST_INSTALL
8) cd ../
9) mkdir packages
10) cd packages
11) mkdir ext
12) mklink /d sysext ../public/typo3_src/typo3/sysext
13) call the website via browsertypo3-test.localhost/ ← TYPO3_PATH_APP
├── typo3_src-14.3.7/
├── packages/
│ ├── sysext -> ../public/typo3_src/typo3/sysext
│ ├── ext/
│ ├── PackageStates.php
│ └── autoload/
├── config/
├── var/
└── public/ ← TYPO3_PATH_ROOT
│ ├── index.php -> typo3_src/index.php
│ ├── typo3_src -> ../typo3_src-14.3.7
│ ├── .htaccess
│ ├── fileadmin/
│ └── typo3temp/Bug 1: Wrong paths in generated autoload files
After installing EXT:news via the Extension Manager:
PHP Warning: include(D:/typo3-test.localhost/public/packages/ext/news/Classes/Utility/ClassLoader.php): Failed to open stream: No such file or directory
Cause: Since
#109470, ClassLoadingInformation passes Environment::getProjectPath() as installation root, so the relative paths are calculated relative to the project path (packages/ext/news/…). The header of the generated files in ClassLoadingInformationGenerator::buildAutoloadInformationFiles() (line 162) still uses the public path, so both are combined into a non-existing path.-\$typo3InstallDir = \\TYPO3\\CMS\\Core\\Core\\Environment::getPublicPath() . ‘/’;
+\$typo3InstallDir = \\TYPO3\\CMS\\Core\\Core\\Environment::getProjectPath() . ‘/’;Bug 2: Public resources of the app package are not allowed
Project path “public/typo3temp/assets/css/7015c8c4ac5ff815b57530b221005fc6.css” is not allowed. Define custom resources if required.
Cause: DefaultAppResources.php defines _assets, uploads and typo3temp/assets with the prefix $relativePublicPath. In Classic Mode, PackageManager::initialize() (line 165–169) creates the VirtualAppPackage with a hard-coded empty string as relative public path. So only typo3temp/assets/… is allowed instead of public/typo3temp/assets/…
$appPackage = new VirtualAppPackage(
$this,
Environment::getProjectPath() . ‘/’,
- ‘’,
+ Environment::getRelativePublicPath(),
);After changing this lines of both, deleted the “var” directory it worked so far as expected.
Added screenshots