Project

General

Profile

Actions

Task #103468

open

Verbose handling when @import 'EXT:site/Configuration/TypoScript/lib/*.typoscript' does not find a file

Added by Christoph Lehmann about 2 months ago. Updated 26 days ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
TypoScript
Target version:
-
Start date:
2024-03-22
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
12
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

The TypoScript backend module has the nice output for syntax checker warnings:

These warnings should produce log messages.

Also "EXT:nonexistent/Configuration/TypoScript," in include_static_file.txt could/should produce warnings.


Files

Actions #1

Updated by Stefan Bürk 27 days ago

I'm not convinced that TypoScript syntax errors should end up in the log or throw
a exception/error in the frontend. First, that would be really spammy if something
slips in and the backend warning is the right way to do it.

In case of the wild-card it could be taken as `optional` but warning about it to
say yeah that is superflous - maybe remove it or add some file.

A missing import never emitted a log entry in the whole time, and I'd say that is
good so. The new interface with v12 make that more visible through the aggregation
on the top.

Actions #2

Updated by Christoph Lehmann 26 days ago

During TYPO3/Extension upgrades and in development context it would be nice to be able to have some warnings/debug messages in the log files. I'm totally on your side, that its noisy when it produces backend notifications and its good that it never was the case.

I don't like muted error message and just think these warnings/errors should not get suppressed in general, but can go to log files.

Actions

Also available in: Atom PDF