«

[Doubler]

Same for me. It only happens in the main window, every 10-12 seconds it pops up again no matter what.

Stop the pain indeed :P

Could it be shoutbox related?
Edit: Propably. A quick shoutbox test showed up in the error report emmediatly.

[Frodo]

Yeah, that's the same message I get. It's SO frustrating. :wallbash:

[Abi79]

That's because you don't let the shoutbox load before you click a link.

[Frodo]

<div class='quotetop'>QUOTE(Abi79 @ Jan 28 2007, 08:20 AM) [snapback]276814[/snapback]</div>

That's because you don't let the shoutbox load before you click a link.
[/b]

The shoutbox doesn't load no matter what I do.

The error message comes, I click on 'OK' to get rid of it. Then just wait about 10 seconds and the message comes back again. The shoutbox still doesn't load.

:wallbash:

[Scatty]

Hmm, I get the message only when I go to a forum part from the main forum. Klicking on OK does it, and it doesn't reappear.

[Japo]

First you shouldn't use MS Internet Explorer, it's just bad. What I experienced once with Opera was the Shoutbox saying: "Initializing shoutbox! Please wait a few seconds while the shouts are retrieved!". And then I got a javascript error, I thought I had copied the error window to the clipboard but I didn't and now the shoutbox loads fine and I'm not able to duplicate the error so I can't show you. But it was a very small window, nothing like the one shown above, and it said something about xajax.js or something like that.

[horrorist]

<div class='quotetop'>QUOTE(Japofran @ Jan 28 2007, 12:00 PM) [snapback]276846[/snapback]</div>

But it was a very small window, nothing like the one shown above, and it said something about xajax.js or something like that.
[/b]

You can generate this message if you just type into your browser: "java script:alert('Error: the xajax Javascript file could not be included. Perhaps the URL is incorrect?\nURL: xajax_js/xajax.js');"
(Don't forget the apostroph and drop the blank between java and script!)

I use opera too, not the very latest version and the shoutbox does not load at all, without any error message.

After looking through the sourcecodes I got to the following:
The shoutbox is launched into an own iframe which is included into a table used to give the page a propper layout. The whole shoutbox is controlled by the xajax.js (a javascript file).
After reading this file I would guess:
The first thing, that script tries to do is to detect the current client and his ability to understand XML by calling the presence of certain active-x objets. Opera (at least the older versions) does not know any active-x object, so the whole shoutbox does not launch.
If the xajax.js detects a suitable activ-x object it actualizes the contents of the shoutbox, which means it requests this contents from the server and includes them into the HTML sourcecode of the shoutbox- page. The contents of the shoutbox seem to be encoded into XML, which is no problem, if you are using MSIE (V 6.0 or higher) or newer Mozilla- Based browsers. If your browser does not parse XML, well bad luck.
This procedure is repeatet every 15 seconds.

Maybe there is a construction error in this script:

r.onreadystatechange=function(){if(r.readyState!=4)
return;if(r.status==200){if(xajaxDebug)xajax.DebugMessage("Received:\n"+r.responseText);if(r.responseXML&&r.responseXML.documentElement)
xajax.processResponse(r.responseXML);else{var errorString="Error: the XML response that was returned from the server is invalid.";errorString+="\nReceived:\n"+r.responseText;trimmedResponseText=r.responseText.replace(/^\s+/g,"");trimmedResponseText=trimmedResponseText.replace(/\s+$/g,"");if(trimmedResponseText!=r.responseText)
errorString+="\nYou have whitespace in your response.";alert(errorString);document.body.style.cursor='default';if(xajaxStatusMessages==true)window.status='Invalid XML response error';}
}

This means the js will detect the HTTP- status. If the status is 200 (OK) nothing will happen. If the status is not 200 the error message allready mentioned by doubler will appear. The handling of other possible status codes are included in the script, but after detecting if the status is not 200. So any status different from 200 (400, 401, 402, 403 - oh I love this... , 404, 500, 501, 502, 503) leads to that errormessage without beeing handled in the right way. If there are no other problems (e.g. 408 - request timeout, 503 - service unavailable) there will be no error messages. Seems that the corresponding else operator has to be placed somewhat later in the script.

Hope that makes sense...

[Lulu_Jane]

I was getting the same shoutbox related error, but it seems to have seems to have stopped now. Very irritating.

[Dave]

I believe you... :blink:

[horrorist]

Well took me at least two hours to crossread the sourcecodes and another four hours to remove those knots out of my brain... :w00t: