Project

General

Profile

Actions

Bug #20965

closed

Field values are not displayed when using bidirectional assymetric m:n relations

Added by Thomas Mammitzsch about 15 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2009-08-31
Due date:
% Done:

0%

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

Description

i use IRRE with bidirectional assymetric m:n relations with

'appearance' => array(
'useCombination' => 1,
),

to create relations to existing childs and have the ability to create new childs which do not yet exist. In Typo4.3 alpha 3 values of existing childs (e.g. title) are not shown in the input fields, when editing inline. If i edit the child directly (not starting with the parent) values are shown correctly. Same TCA setup works fine in Typo 4.2.6 with using IRRE.

(issue imported from #M11837)

Actions #1

Updated by Thomas Mammitzsch about 15 years ago

This bug happens if there is more than 1 child and it behaves the same also for 1:n relations.

Actions #2

Updated by Thomas Mammitzsch about 15 years ago

i get an error thrown in 4.3 when i display the TCEform:

Fehler: uncaught exception: [Exception... "An invalid or illegal string was specified" code: "12" nsresult: "0x8053000c (NS_ERROR_DOM_SYNTAX_ERR)" location: "http://projekte.test/vierdrei/typo3/contrib/prototype/prototype.js Line: 2844"]

in 4.2.6 i don't get this error so i assume thats the bug..

Actions #3

Updated by Thomas Mammitzsch about 15 years ago

The bug is caused by scriptaculous 1.8.2, which comes with Typo 4.3 alpha 3.
If i use scriptaculous 1.8.1 from 4.2.6, everything works fine

Actions #4

Updated by Martin Holtz almost 15 years ago

same issue was in #21646

try if it works in IE7 or FF 3.0.

reason was there the new javascript function querySelector which is supported by IE8 and FF3.5. That function does not allow an selector with brackets [ ].

i disabled that part in prototype 1.6.0.3 everything seems to be fine again:)

Actions #5

Updated by Stefan Galinski over 11 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)
Actions #6

Updated by Alexander Opitz over 11 years ago

  • Status changed from Needs Feedback to Closed

IMHO this bug was resolved with #21349 in the 4.3 line later on => closed.

Actions

Also available in: Atom PDF