Project

General

Profile

Actions

Bug #21205

closed

deleting of Irre Elements does not work

Added by Sven Juergens over 14 years ago. Updated over 5 years ago.

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

0%

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

Description

in current trunk 6109 of TYPO3 4.3
it's not possible to deleted an Irre Element, if you click the garbage Icon.

Firebugs Error Message :
An invalid or illegal string was specified" code: "12
[Break on this error] results = $A(root.querySelectorAll(e)).map(Element.extend);\n
prototype.js (Zeile 2844)

to reproduce,

install current trunk of TYPO3 4.3
-install Extension irre_tutorial
go to Module "IRRE Turorial" and install sample Data
- got to page "1:n comma separated values"
- edit the record "Wellness Well-Being Hotel Rose..."
- try to delete one of the IRRE Elements ""Experience it" Week", or "Wellness & Beauty Week" with the Garbage Icon

(issue imported from #M12152)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #21349: DOM object identifiers use invalid charactersClosedOliver Hader2009-10-23

Actions
Actions #1

Updated by Sven Juergens over 14 years ago

it seems there is a problem with Firefox 3.5.3 on Windows an MAC, with FF 3.0.14 there is a normal behavior.
yout can test it with a portable Firefox version

Actions #2

Updated by Alexander Stehlik over 14 years ago

I can confirm this bug for TYPO3 4.3beta2 in Firefox 3.5.3 running on Ubuntu 9.04.

In Epiphany everything works fine.

The error occurs in t3lib/jsfunc.inline.js in line 671 in this function call:
inlineRecords = Element.select(objectId+'_div', '.inlineRecord');

Actions #3

Updated by Oliver Hader over 14 years ago

This problem was solved in the current SVN Trunk and will be released with TYPO3 4.3-beta3.
Please report again, if the current SVN Trunk still has a problem here...

Actions #4

Updated by Sven Juergens over 14 years ago

with current trunk (6287) the bug is solved

Actions #5

Updated by Alexander Stehlik over 14 years ago

Everything looking good in the current trunk :)

Actions #6

Updated by Oliver Hader over 14 years ago

Great! Thanks for your feedback! :)

Actions #7

Updated by Oliver Hader over 14 years ago

This issue was solved with RFC #21349

Actions #8

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF