Project

General

Profile

Actions

Bug #18751

closed

JavaScript error in TBE_EDITOR causes login expired dialog

Added by Anders Viskum over 16 years ago. Updated about 16 years ago.

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

0%

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

Description

After upgrading from Typo3 4.1 to 4.2.0 we are getting login expired-errors:
"Your login has probably expired. Do you want to refresh now?"

The error occurs in different situations, but often when changing the template for a site..

(issue imported from #M8336)


Files

0008336.patch (1.52 KB) 0008336.patch Administrator Admin, 2008-05-13 11:50

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #18429: required fields in Flexform are not correct marked with Exclamation SignClosed2008-03-12

Actions
Has duplicate TYPO3 Core - Bug #18427: Required fields within flexform section elements cause Javascript errorsClosedOliver Hader2008-03-11

Actions
Actions #1

Updated by Andy over 16 years ago

For me this only happens, if the RTE is enabled

Actions #2

Updated by Dmitry Dulepov over 16 years ago

Not reproducable for me. Possibly browser-dependent

Actions #3

Updated by Oliver Hader over 16 years ago

Could you please give a step by step example how it can be reproduced on your side?
Did you experience any JavaScript errors?

Actions #4

Updated by Anders Viskum over 16 years ago

I get the error every time I am using the plugin daimi_event and editing an event. It happens sometimes then editing a template or text element on a site, but this is not reproduceable.

The javascript errors:
document[TBE_EDITOR.formname][elementName] has no properties
in jsfunc.tbe_editor.js line 197

We have tested in both firefox, IE and Safari...

Actions #5

Updated by Steffen Kamper over 16 years ago

we had such an error with cal in the past. This was result of creating a dummy BE_USER to do some actions, so i guess that the problem belongs to the extension you use.

Actions #6

Updated by Oliver Hader over 16 years ago

Please test the attached patch which first checks whether the form field exists and then accesses the value property.
It seems that it is a misconfiguration in your extension (a field which is marked to be required but not rendered at all in the forms view).

Actions #7

Updated by Anders Viskum over 16 years ago

Thx a lot Oliver.. the patch fixed the problem. Are you updating the Typo3-src with the fix?

Actions #8

Updated by Steffen Kamper over 16 years ago

sure, RFC is in core list.

Actions #9

Updated by Oliver Hader over 16 years ago

Committed to SVN:
  • TYPO3_4-2 (rev. 3743)
  • Trunk (rev. 3744)
Actions

Also available in: Atom PDF