Xinha Discussion Forum

cschults

New member

Registered: 2007-02-08

Posts: 1

What does callbackIfNotReady do?

I successfully added Xinha to our blog, which is 'gristmill.grist.org'. Yesterday, I then attempted to also add it to our website 'www.grist.org' by referring to the files located under our blog subdomain. My first mistake was to use relative paths for the core and custom config JavaScript files. That obviously didn't work, so I made the paths absolute. What I didn't realize is that the core JS file had references to other JS files, one being 'functionsIE.js'. Thus, I was seeing a lot of 404's for 'functionsIE.js' as it was looking for it under the wrong subdomain. So I removed the code that loaded the core and custom config JS files, but the 404's for 'functionsIE.js' continued -- and I had no clue why. I stopped the 404's by creating an empty file.

This morning, I took a look at the code to try to figure out what might have caused the persistent requests for 'functionsIE.js'. In 'XinhaCore.js', I found this reference to 'functionsIE.js':

Xinha._loadback(_editor_url + "functionsIE.js",callbackIfNotReady);

Being the JavaScript novice that I am, I'm not sure what 'callbackIfNotReady' does. I'm wondering, in this case, if it continued to make attempts to load 'functionsIE.js' after the original request.

Could someone explain what 'callbackIfNotReady' does? And if not the cause, why there were continued requests for 'functionsIE.js' even after I removed all references to 'XinhaCore.js' and our custom config script?

Thanks,

Chris

ray

Xinha Administrator

From: Germany

Registered: 2005-03-23

Posts: 521

Website

Re: What does callbackIfNotReady do?

it continued to make attempts to load 'functionsIE.js' after the original request.

Yes, this is basically what it does.

This part however has been changed in the meantime.

After all you would have to set the _editor_url in a way that the files can be accessed