Project

General

Profile

Actions

Bug #49354

closed

Call to undefined method TYPO3\CMS\Backend\Form\ElementConditionMatcher::setRecord()

Added by Frans Saris almost 11 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2013-06-23
Due date:
% Done:

100%

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

Description

In the change "[TASK] Extract displayCond functionality from FormEngine to new class" the TYPO3\CMS\Backend\Form'FormEngine->isDisplayCondition() broke.

Resulting in:

Fatal error: Call to undefined method TYPO3\CMS\Backend\Form\ElementConditionMatcher::setRecord() in typo3_src-6.1.0/typo3/sysext/backend/Classes/Form/FormEngine.php on line 5954

When adding a condition to the sheet section of a flexform like in forge.typo3.org/issues/33390#note-8

Why is this function deprecated when it's still used for rendering flexforms?


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #46461: Extract displayCond functionality from FormEngine to new classClosed2013-03-20

Actions
Actions #1

Updated by Gerrit Code Review almost 11 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/21605

Actions #2

Updated by Gerrit Code Review almost 11 years ago

Patch set 2 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/21605

Actions #3

Updated by Christian Kuhn almost 11 years ago

+1 ... BTW: the method is not used in the core, this is probably some extension that caused this for you, the fatal however needs to be fixed.

Actions #4

Updated by Gerrit Code Review almost 11 years ago

Patch set 1 for branch TYPO3_6-1 has been pushed to the review server.
It is available at https://review.typo3.org/21615

Actions #5

Updated by Frans Saris almost 11 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #6

Updated by Frans Saris almost 11 years ago

Christian Kuhn wrote:

+1 ... BTW: the method is not used in the core, this is probably some extension that caused this for you

Oke, sorry for my wrong/to quick assumption.

the fatal however needs to be fixed.

Tnx all for taking care.

Gr. Frans

Actions #7

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF