Project

General

Profile

Actions

Bug #70297

closed

Story #69617: FormEngine bugs

Placeholder config with default value of related record field fails

Added by Philipp Wrann over 8 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Must have
Category:
FormEngine aka TCEforms
Target version:
Start date:
2015-10-02
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
7
PHP Version:
5.6
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Just updated to 7.5, now i get many catchables like:
Core: Error handler (BE): PHP Warning: explode() expects parameter 2 to be string, array given in .../typo3/cms/typo3/sysext/backend/Classes/Form/FormDataTraverser.php line 140

backtrace attached.

The field config:
'type' => 'input',
'eval' => 'null,trim',
'placeholder' => '__row|detail_type|title',
'mode' => 'useOrOverridePlaceholder',
'default' => NULL


Files

trace.txt (6.64 KB) trace.txt Philipp Wrann, 2015-10-02 10:39

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #70146: Input placeholder record traversal is brokenClosedMorton Jonuschat2015-09-28

Actions
Actions #1

Updated by Morton Jonuschat over 8 years ago

  • Status changed from New to Needs Feedback

I'm already on that but I'm having trouble reproducing it. Can you provide a bit more detail about the TCA or maybe even a simple test extension that reproduces this?

Actions #2

Updated by Philipp Wrann over 8 years ago

The field detail_type is defined as select, that seems to be the problem, if it is defined as group|db everything works.

BUT then no onchange event is fired and i can not use the requestUpdate feature anymore.

Actions #3

Updated by Philipp Wrann over 8 years ago

If you change the relation type of sys_file_reference|uid_local to select it should break.

Actions #4

Updated by Morton Jonuschat over 8 years ago

Thanks, i'll try to reproduce with the added information

Actions #5

Updated by Frans Saris over 8 years ago

FormDataTraverser->getFieldValue() doesn't handle nested relations correctly.

For instance when looking at sys_file_reference.title.placeholder = __row|uid_local|metadata|title the uid_local is found but the the next step fetching the correct metadata record fails

Actions #6

Updated by Frans Saris over 8 years ago

Looks like the code can not find the correct metadata record. It always finds the first record from sys_file_metadata table.

edit looks like the reason for that is because I set the metadata value of sys_file to 1

Actions #7

Updated by Frans Saris over 8 years ago

Ok, looks like getRecordRow() returns a flat db record where metadata holds only the reference count but getRelatedInlineFieldUids() expects a value like "The value in the local table (normally a comma separated list of the inline record UIDs)."

Actions #8

Updated by Christian Kuhn over 8 years ago

  • Parent task set to #69617
Actions #9

Updated by Morton Jonuschat over 8 years ago

  • Status changed from Needs Feedback to In Progress
  • Assignee set to Morton Jonuschat
  • Priority changed from Should have to Must have
Actions #10

Updated by Gerrit Code Review over 8 years ago

  • Status changed from In Progress to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/43795

Actions #11

Updated by Gerrit Code Review over 8 years ago

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/43748

Actions #12

Updated by Gerrit Code Review over 8 years ago

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/43748

Actions #13

Updated by Gerrit Code Review over 8 years ago

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/43748

Actions #14

Updated by Markus Klein over 8 years ago

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

Updated by Riccardo De Contardi over 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF