Hmm - are you SURE that the IE8 cache is cleared? If the new javascript for concrete5.4 weren't loaded you'd definitely get that error.

Are there other javascript errors on the page when you're updating the block? Does this happen to other blocks/all blocks or just to a custom one?

Hi Andrew,

It just happens with the custom block, all other blocks seem to work fine. And I don't see any javascript errors!

Even in IE8 the block is updated, so it works! Just the redirection or refreshing of the page doesn't seem to work.

I also tested it with the developers mode in Chrome and it doesn't give any kind of error.

Cache could be a problem, I'll test it again.

Thank you so far...

Same problem (5.4.0.5):

Page reload after inserting or editing a block of simpleNews addon does not work in IE8. Content block for me works fine??? No problem occurs in Firefox.

Only JSON String is shown (no html code, javascript error and so on). Really hard to debug... BUT A BIG PROBLEM FOR ME!!! Maybe i temporary go back to Version 5.3.3.2. Seems to be more stable.

Don't think that it is a caching problem. Tried to clear every cache. Problem still exists.

Please try to fix!
THX Marc

I have been racking my brian as I am having this issue on all the simple addons as well. only on ie8

do your blocks use either an instance or a copy of the WYSIWYG content editor?

Chad

Hi Chad,

No, sorry..... I didn't figure it out yet...

TinyMCE isn't causing the problem. I tried this already...

I think it's coming from the javascript, but I'm not sure. The fact that you don't get an error is frustrating... No error, no problem...right!?

Maybe we can ban IE (all versions), the world would be better of.... :-)

My work around: Force IE8 to behave like IE7...

Add the following meta tag to your page type files (default.php, etc.)

<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />

Please try to fix this problem!!!

Best regards.
Marc

I think I have this resolved for my forms. I believe it was that my select options in my form did not have a value. I had <option>value</option>, and the ajax request was requiring a value. <option value=value>value</option>

Chad

Thanks Chad,

But I haven't got any selectionboxes. But maybe it could help me. Seems that ajax doesn't like empty values.

So I'll change the code so no empty values are being transferred. See if it works...

I'll keep you guys posted...

-- BUMP --
I'm seeing this on FF12.0 when debugging a site built with Concrete 5.5.2.1.

Any help would be greatly appreciated.

thanks
~o~

I know this thread is very old, but just in case someone still encounters this problem (as I did...), perhaps this may be a hint:

The json-line is returned by the process storing a new or updated block. As blocks are stored with an ajax call it just prints a json object as return for the ajax call (find it in /concrete/startup/process.php line 804 for version 5.6.3.2).
Now if the json object is displayed in the browser window rather than processed by a javascript call, this implies that the block's add/update form was submitted without using ajax. And this implies that javascript crashed somewhere before.

At least in my case this was the problem. There was an error in the auto.js file of my blocktype, and since auto.js is loaded dynamically no message was displayed in the console.