SchweppesAle Posted June 10, 2009 Share Posted June 10, 2009 seem to be receiving the same error message on multiple pages(under IE). the line: and char: references don't seem to match up with any object tags though. I was hoping someone could point out what's causing the problem. url: http://www.theprogressiveaccountant.com/management-features/ that's just one example though. Quote Link to comment Share on other sites More sharing options...
KevinM1 Posted June 10, 2009 Share Posted June 10, 2009 seem to be receiving the same error message on multiple pages(under IE). the line: and char: references don't seem to match up with any object tags though. I was hoping someone could point out what's causing the problem. url: http://www.theprogressiveaccountant.com/management-features/ that's just one example though. Unfortunately, baffling error messages are what IE is known for. Double unfortunately, I didn't get any errors in FF, so I can't use Firebug to point me in the direction of where your error lies. I'm guessing, since the error is being reported right at the beginning of the document, that either it's choking on some library/framework code, or one of the initial lines of your code. Specifically, I'd look to see if the Mootools addEvent function is behaving properly. You should also double-check that your various bits of library code can co-exist with one another. There's a chance that there's a pesky interoperability issue that IE can't resolve. If the problem persists, the only thing I can suggest is to create a fresh page as a test bed. Add each external .js file to it and test it before moving to the next. As you slowly rebuild your code in that test page, you should be able to detect when the error pops back up, which should (hopefully) give you an idea of what the culprit is. Quote Link to comment Share on other sites More sharing options...
SchweppesAle Posted June 11, 2009 Author Share Posted June 11, 2009 thanks, I appreciate your help anyway. I'll probably just take the site down when there's low traffic and disable each bit of code like you said. I'm sure it's something minor since the page appears to be rendering correctly anyway. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.