Skip to content

Conversation

NamelessCoder
Copy link
Member

Prevents deprecation log flooding without requiring massive API changes.

@NamelessCoder NamelessCoder force-pushed the feature/deprecation-fixes branch from a4f1bfa to 60576b5 Compare September 1, 2025 11:59
Prevents deprecation log flooding without requiring massive API changes.
@NamelessCoder NamelessCoder force-pushed the feature/deprecation-fixes branch from 60576b5 to b6b262d Compare September 1, 2025 12:03
@NamelessCoder NamelessCoder merged commit 3906db8 into FluidTYPO3:development Sep 1, 2025
16 checks passed
@NamelessCoder NamelessCoder deleted the feature/deprecation-fixes branch September 1, 2025 12:05
@liayn
Copy link
Contributor

liayn commented Sep 4, 2025

Seems like this changed killed v:render.uncache

Thu, 04 Sep 2025 09:36:35 +0200 [ALERT] request="d124be27c990a" component="TYPO3.CMS.Frontend.ContentObject.Exception.ProductionExceptionHandler": Oops, an error occurred! Code: 20250904093635450d5026- InvalidTemplateResourceException: Tried resolving a template file for controller action "Default->Default" in format ".html", but none of the paths contained the expected template file (Default/Default.html). No paths configured., in file /var/www/html/web/vendor/typo3fluid/fluid/src/View/TemplatePaths.php:617 - {"exception":"TYPO3Fluid\Fluid\View\Exception\InvalidTemplateResourceException: Tried resolving a template file for controller action "Default->Default" in format ".html", but none of the paths contained the expected template file (Default/Default.html). No paths configured.

At least this happened, when we updated from 7.1.3 to 7.1.4

@NamelessCoder
Copy link
Member Author

Pretty sure this change isn't the one causing a problem with v:render.uncache. Can you try reverting commit 68d84ad to see if that solves the problem?

@liayn
Copy link
Contributor

liayn commented Sep 4, 2025

Right, I clicked the wrong PR, sry. Yes,
68d84ad#diff-38f5ddad84242dbb78f7a031ac97a0ba3df9c4e58476fa3007d5e88bbaf99948L117
is the culprit in our case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants