Brian,
Things seem fine in my Firefox, but I started getting calls
from EI users. When I opened it is EI I got errors that
others were not reporting so I think it might be my IE
settings.

I am curious why this works great in FireFox, but not IE and
can you give me insight as to why these errors come up:




Thanks,

Tim

What did you do to get it working on that server may I ask?

As far as the IE error, it say error on "inject after" which
I am not using. So it may be coming from another module conflicint
with the moolet.

Try creating a new page with no modules assigned expect the
moolet and see if it runs without error. If so turn on your
modules one by one and see which one should not share the same
page. Maybe that weather one?

There is a chance the mootools itself is using inject after on
my moolet even though I use another call. In which case I would
not know.


Let me know how that test comes out and what you did to get
this working on that host please

thanks

Tisk, tisk, tisk! Only us obsessive types are working on a Satuday.

That is why I got out of retail and into computers and see where I am now!

Anyway, I am not sure what I did other than what you prescribed
to Swiftek. It started working in Firefox when I pointed the
ShoutBoard to the proper Moo...js.

So, right now my only issues are that it doesn't load in IE on nany
page or in the FireBoard forum in any browser.

By the way, am I breaking any rules by altering the animated GIF
for the loading? If so I can change it back, but I like the biker-dude
a little better.



My issue must lay with the compatibility with ShoutBox since all
was well until I installed that yesterday. I will keep looking at
what might be causing this, but do not have the time of experience
to look into this too much. Any advice would be greatly appreciated

Brian,
I am sorry to bother you again about this, but I am at my wits end. Thus, I am hoping that you might have some insight into what is going on. Here is what is happening and what I have done so far:

• I installed moo's Online. I always use FireFox, so I don't know if it worked in IE or not, but all was well in FireFox.
• I installed ShoutBox and we had some issues in both browsers. This was the first I heard about the problems in IE, but that doesn't mean they weren't there all along
• I was able to fix the problem in FireFox by pointing the ShoutBox from the outdated mootools.js to mootools.v1.1.js, but IE continued to have issues -- it loads but says 'Moolets Loading' forever and you can not see who is on line.
• I uninstalled ShoutBox, no change in IE.
• I reinstalled ShoutBox and made the js change, no change in IE
• I uninstalled, then re-installed the moo's Online Moolet 1.1, no change in IE
• Thinking that IE might not be parsing the apostrophe in the _title_ properly I renamed it to Who Is Online, no change in IE
• Thinking there might be some tag mismatch in my index.php I scoured that file and found (and fixed) a couple of unclosed tags, but no change in IE

Nothing else on my site uses AJAX, so I don't know what else it could be. When I try to look at the js file is it all on one line and very hard for me to try to troubleshoot.

Do you have any suggestions? :_b_link__: Even wacky things to try or look for? Is there something besides AJAX that uses Moolets?

Please advise
The site again is www.TwinCitiesSpoke.com

Thanks a ton,
Tim

OK, I missed one piece -- the Current Conditions. When I removed that one I lost the injectAfter error, but still have an error on the same line (132) as the injectAfter error was. Don't know if that helps or not.

REVISED:
I unpublished all of the modules on my site and re-published them one by one to see if there were any errors. There were only two modules that had errors -- the moo's Online and ShoutBox (both using the same js file mootools.v1.1.js). If I switch to the mootools.js that came with the Shoutbox, then I get the error described above where I lost the injectAfter error.

The moolet needs mootools 1.1 and the old shoutbox needs 1.0 so they should not be on the same page.

On the "IE" Issue.
Sorry, Internet Destroyer (IE) sucks in a real bad way. I have been a web developer for 12+ years and there is still no dealing with that monster.

There can something simple like a change in a web server setting on apache or IIS that can even damage a site for IE that has nothing to do with your or your settings.

There is no way for me to trace these kind of problems. With firefox there is FireBug that tells me all.

With IE all problems can be gone and the mother still will not work if it chooses not to.


Sorry, clueless here...