Project

General

Profile

Actions

Bug #100345

closed

Unable to get property "type" of non-object "getTSFE()"

Added by Andreas Nedbal over 1 year ago. Updated about 2 months ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
TypoScript
Target version:
-
Start date:
2023-03-29
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
12
PHP Version:
8.1
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Following condition is breaking in 12.3 (this is not a 12-compatible repository however, as a notice for testing/evaluating)
https://github.com/einpraegsam/powermail/blob/develop/Configuration/TypoScript/Powermail_Frontend/setup.typoscript#L116

According to the documentation getTSFE() should evaluate to false if it's not available in a given context. This seems to happen here, but it still tries to access the type property afterwards, leading to an exception.


Related issues 2 (1 open1 closed)

Related to TYPO3 Core - Task #100047: Modernize condition matching / expression handlingClosed2023-02-28

Actions
Related to TYPO3 Core - Bug #105191: TypoScript condition with missing traverse breaks log moduleUnder Review2024-10-04

Actions
Actions #1

Updated by Andreas Nedbal over 1 year ago

  • Description updated (diff)
Actions #2

Updated by Andreas Kienast over 1 year ago

  • Status changed from New to Needs Feedback

Can you please check whether using traverse() solves the issue?

Actions #3

Updated by Christian Kuhn over 1 year ago

Using traverse() should fix this. v12 no longer suppresses according warnings and forces integrators to fix conditions. Please feedback if that solves your issue.

Actions #4

Updated by Christian Kuhn over 1 year ago

  • Related to Task #100047: Modernize condition matching / expression handling added
Actions #5

Updated by Andreas Nedbal over 1 year ago

Using traverse() indeed fixed this. Thanks for the hint!

Actions #6

Updated by Georg Ringer over 1 year ago

  • Status changed from Needs Feedback to Closed

closing issue as it can be solved by proper condition usage

Actions #7

Updated by Lina Wolf about 2 months ago

I think this is an example of a non-helpful error message. I am wondering cannot we catch this earlier and output a meaningfull error message?

Actions #8

Updated by Lina Wolf about 2 months ago

  • Related to Bug #105191: TypoScript condition with missing traverse breaks log module added
Actions

Also available in: Atom PDF