Details
-
Task
-
Resolution: Fixed
-
None
-
None
-
Empty show more show less
Description
Once upon a time we tried to implement a JS logging for one specific JS error. In the past the following error happened sometimes: the opened segment and the segment to save was differing, which was really strange and dangerous since a segment was overwritten with the content of a different segment.
The error disappeared - probably with a past ExtJS update. Now the error was coming up again, but the own logging does not give any useful information for the background.
The log message starts with the following subject:
'Zend_Exception' with message 'Fehler im Javascript. Die folgende Meldung wurde vom JS übergeben: Das Segment konnte nicht zum Bearbeiten geöffnet werden...
So in favour of using therootcause this own logging should be removed, so that more information can be collected to the originating error.