Project

General

Profile

Actions

Bug #18687

closed

JavaScript Errors in Safari so no editing and creating possible

Added by Sven Weiss about 16 years ago. Updated about 16 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
-
Start date:
2008-04-24
Due date:
% Done:

0%

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

Description

If I try to edit a Page Content Element then I get the error:
TypeError: Value undefined (result of expression TBE_EDITOR.addNested) is not object.
http://172.16.153.134/typo3/alt_doc.php?returnUrl=db_list.php%3Fid%3D37%26table%3D&edit[tt_content]61=edit (line 732)

Then I see no values of input fields and textareas. The RTE also doesn't load. The inputs are all empty.
Also if I create a new Content Element:
TypeError: Value undefined (result of expression TBE_EDITOR.addNested) is not object.
http://172.16.153.134/typo3/alt_doc.php?returnUrl=db_list.php%3Fid%3D37%26table%3D&edit[tt_content]37=new (line 646)

(issue imported from #M8228)

Actions #1

Updated by Martin Seebach about 16 years ago

I can confirm this in Ubuntu Linux Firefox 2.0

The error is:
Error: TBE_EDITOR.addNested is not a function
Source File: http://www.xxxxxxxxxxxxx.dk/typo3/alt_doc.php?returnUrl=%2Ftypo3%2Fsysext%2Fcms%2Flayout%2Fdb_layout.php%3Fid%3D314&edit[fe_users]3280=edit
Line: 917

Actions #2

Updated by Martin Seebach about 16 years ago

OK, solved.

Another error is:
Error: uncaught exception: script.aculo.us requires the Prototype JavaScript framework >= 1.6.0

Downloading a new Prototype and putting it in typo3_src/typo3/contrib/prototype/prototype.js solved it all.

Actions #3

Updated by Ingo Renner about 16 years ago

1. How did you fix it?

2. You probably just need to clear your browser's cache, TYPO3 4.2 comes with prototype 1.6.0.2 already!

Actions #4

Updated by Martin Seebach about 16 years ago

I solved it by replacing the prototype library, but you're absolutely right that 4.2 ships with 1.6.0.2, so the /real/ solution was clearing the browser-cache.

Actions #5

Updated by Sven Weiss about 16 years ago

Can confirm it: Cleared Browser Cache (in my case Proxy Cache) and it was ok

Actions #6

Updated by Oliver Hader about 16 years ago

So, this isn't a bug at all and can be closed, right?

Actions #7

Updated by Martin Seebach about 16 years ago

Agree.

Actions

Also available in: Atom PDF