Project

General

Profile

Actions

Bug #81675

closed

IRRE Standard Typo3 CE Localization

Added by Eduard Luft almost 7 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
-
Target version:
-
Start date:
2017-06-22
Due date:
% Done:

0%

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

Description

Hello, actually i'm trying to update a Typo3 6.2 website to Typo3 7.6. (actually Typo3 7.6.19)

While testing the localization with IRRE CE I found a bug. This bug only appears with Typo3 standard elements.
The backend view from the Plugin

If I hit the localize button, it seems nothing happens.
But in real, the CE gets translated and a correct n:m connection is set.
Just the ajax don't change the frontend view of the backend.
If I hit now the save button, it will save the actually view & delete the n:m connection...
If I hit the close button and enter the CE again, I will see the localized CE and everything is fine.

I debugged a bit of the core with the help of this response information.
There is a scriptCall1 Ext.onReady.... which makes problems.
That one calls a JS function with TypeError: Cannot read property 'dom' of null. !JS Error.png!

I'm catching that error and returning true to skip that. (hackJs.png).
And the result is kind of nice, CE gets localized but the categories tab is empty.


Files

Basic_Mask.png (30.6 KB) Basic_Mask.png Eduard Luft, 2017-06-22 09:33
Response.png (223 KB) Response.png Eduard Luft, 2017-06-22 09:44
JS Error.png (51.2 KB) JS Error.png Eduard Luft, 2017-06-22 09:47
hackJs.png (19.3 KB) hackJs.png Eduard Luft, 2017-06-22 09:48
Categories.png (22 KB) Categories.png Eduard Luft, 2017-06-22 09:49
Actions #1

Updated by Chris topher almost 7 years ago

  • Project changed from 24 to TYPO3 Core
  • TYPO3 Version set to 7
Actions #2

Updated by Andreas Kienast almost 7 years ago

  • Description updated (diff)
Actions #3

Updated by Benni Mack about 6 years ago

  • Status changed from New to Needs Feedback

We fixed this in v8, can you please test again in v8 if this error still occurs?

Actions #4

Updated by Riccardo De Contardi almost 6 years ago

  • Status changed from Needs Feedback to Closed

No feedback since the last 90 days => closing this issue.

If you think that this is the wrong decision or experience the issue again and have more information about how to reproduce your problem, please reopen it or open a new issue with a reference to this one.

Thank you and best regards

Actions

Also available in: Atom PDF