Issue Bug New Quiet

#111360Failed YAML imports make a site invalid in a 14.3 patch release

Simon Schmidt 11/06/26, 16:29 updated 11/06/26, 16:29

Description

Related to #110913 (Broken site configurations are skipped and reported).
Regression of #88993 (Catch possible exceptions while loading YAML files via import).

The soft-fail for broken sites is a good improvement.
But the change also reverts the behaviour of #88993 for site configurations in 14.3.x.

  1. says: “If an error happens during loading YAML files, e.g. because the path
    is wrong or the used extension has been deactivated, the website must still be working.”

With RETHROW_IMPORT_EXCEPTIONS, a failed import now makes the complete site invalid.
This applies to config.yaml, settings.yaml and csp.yaml.

A failed import can be:

- an imported file that does not exist or is not readable
- an imported file with a YAML syntax error
- a wildcard such as “*.yaml” without “glob: true”. This import never loaded a file.
Before, nobody noticed it. Now, the site is invalid.
- an import with “EXT:” of an extension that is not active

Example: an extension writes data into a separate file in a shared directory.
settings.yaml imports this file. The file does not exist before the first write.
After the update to the new release version from 14.3, the site is not available until the file exists.

The result for the site:

- The frontend of the site is not available.
- The changelog says that another site with a less specific entry point
(for example “base: ‘/’”) can handle the requests for the domain.
Thus the domain can show the content of a different site.

This change occurs in a patch release.
The changelog is “Important”, not “Breaking”.
Administrators do not expect this change in a patch release.

Suggestions:

1. Keep the old behaviour for failed imports in 14.3 (log and ignore).
Use RETHROW_IMPORT_EXCEPTIONS only in v15.
2. If the behaviour stays in 14.3: tell administrators about it in the release notes of the next 14.3 release.
For example:
– Before the update, search the log for “could not be loaded” and “has syntax errors”.
– After the update, run “vendor/bin/typo3 site:validate” in the deployment.
– For an optional import, use “glob: true”. A glob without a match is not an error.
3. Document “glob: true” as the correct way to write an optional import.

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] Failed YAML imports make a site invalid in a 14.3 patch release Resolves: #111360 Releases: main

History 2