Easy Edit Suite - Content Edit fails to open with error 80020101

Squiz Matrix Support
1

Can anyone tell me what could be the cause of this error, please?

 18.161s: CHECK READ ONLYfalse
 0.01s: API queuegetKeywordsReplacements 
 0s: API CALL: getKeywordsReplacements 
SCRIPT5009: 'bodycopy_current_data' is undefined 
_edit, line 98 character 3
SCRIPT257: Could not complete the operation due to error 80020101. 
easyedit.min.js, line 11 character 11496

Easy Edit suite fails to open the Content Edit window, with the above error appearing in the javascript console.

 

(Details:

squiz Matrix v4.12.2

EES Build 1858)

 

Thanks.

2

Are you using IE?

3

It's likely that it's having difficulty parsing the JSON formatted content returned by the JS API, especially if this is the only asset where the error is occuring.

 

To debug further, when the error appears can you check the bottom left corner of the interface for any EES error reports? There will be a red icon you can click on, and then a 'more information' link which will reveal a detailed error report (including browser version, asset information etc).

 

It may also be useful to look at the contents of the asset, which might reveal more information about the cause.

4

Are you using IE?

 

The format of the errors provided suggest that it is IE9 or IE10, one of the two.

 

It's likely that it's having difficulty parsing the JSON formatted content returned by the JS API, especially if this is the only asset where the error is occuring.

 

This is likely what is happening - unfortunately if there is a syntax error (or even a PHP error of some sort) in what is being returned through the API, it appears that all IE will give you is this "80020101" internal error code.

 

It's possible (and quite likely) that the error preceding it is related to it - "bodycopy_current_data" is not in EES, but rather the Bodycopy asset type's JS code - so I will also take a look to see if anything in there has been fixed.

 

I will take a look into it as far as I can, but additional information of the type Anthony mentioned would help too.

5

Thank you Nic, Anthony and Luke.

 

Yes, the error message that I submitted above is from IE 10

 

but checking in other browsers yields these errors:

Safari   5.1.7
8.568s: CHECK READ ONLY [false]
easyedit.min.js:3720s: API queue ["getKeywordsReplacements"]
easyedit.min.js:3720s: API CALL:  ["getKeywordsReplacements"]
ReferenceError: Can't find variable: bodycopy_current_data

and

Google Chrome:Version 27.0.1453.110 m
11.481s: CHECK READ ONLY Array[1] easyedit.min.js:372
0.001s: API queue Array[1] easyedit.min.js:372
0s: API CALL:  Array[1] easyedit.min.js:372
Uncaught ReferenceError: bodycopy_current_data is not defined 

But in Firefox (21.0) the editor works.

(But Unfortunately, the client's staff are not permitted to have Firefox on their computers)

 

 

It's likely that it's having difficulty parsing the JSON formatted content returned by the JS API, especially if this is the only asset where the error is occuring.

 
To debug further, when the error appears can you check the bottom left corner of the interface for any EES error reports? There will be a red icon you can click on, and then a 'more information' link which will reveal a detailed error report (including browser version, asset information etc).

 

In IE, Safari and Chrome the error occurs the same on the several pages that we tested.

When the error occurs, the black screen with the rotating icon shows until it times out.

Clicking the continue link on the timed out dialog shows the editor page with no content.

and there's no red icon to click on.

 

 

t's possible (and quite likely) that the error preceding it is related to it - "bodycopy_current_data" is not in EES, but rather the Bodycopy asset type's JS code - so I will also take a look to see if anything in there has been fixed.

 

Yes, It seems clear that the bodycopy content is not being loaded.

 

I had a look at the Javascript information using the Firefox developer tools to confirm that all of the JavaScript is being served from the same domain.

 

I found that the file "/system/core/js_strings.en.js" is being served from the System Static URL (which has a different domain name), while all the other JavaScript is being served from the same domain as the page that we are attempting to edit.

 

Is it possible that that is contributing to this problem?

 

 

The pages that we are attempting to edit are fairly ordinary  "standard pages", each with only one div...  and a couple of them have text only with no images.