"Done, but with errors on page." with IE6 & IE7

I’m wandering if you guys do any of your development in multiple browsers. I have no problems with Firefox but I get repeated errors in both IE6 and IE7.

In both IE6 and IE7 I’m getting this, "Done, but with errors on page." This happens while I’m logged out and it happens on any page.

MODxHost and MODxHostWithComments work just fine but in all other templates, MODxCSS, and MODxCSS Wide and all of it’s alternate styles have this error. I was able to track this down to the very last line of /assets/snippets/ajaxSearch/js/ajaxSearch.js. When I commented out the last line this error stopped. I don’t know how to fix this and I’m sure someone will have input.

And for the next error. This error happens when I’m logged in and it happens on any page.

This is in one of these files
/manager/media/script/mootools/mootools.js
/assets/modules/quick_edit/javascript/QuickEdit.js
/assets/modules/quick_edit/styles/toolbar.css

Same thing as before this all works fine with MODxHost and MODxHostWithComments but in all other templates, MODxCSS, and MODxCSS Wide and all of it’s alternate styles have this error.

Like i said, I don’t know anything about javascript and I’m hoping someone may be able to help me fix this.

Wow! No one has any input at all?

The demo templates haven’t been looked at in a long long time. I’d be surprised honestly if these were the only errors. Hmmm ... I smell a contest brewing...

The demo templates are not the problem. What the problem is is the javascript files and how they are being called by the templates. These errors that IE is reporting are javascript errors and not template errors.

I did state that I don’t know javascript and what I had to do to fix these errors being reported by IE was to comment the last line in ajaxSearch.js and disable the QuickEdit plugin. The QuickEdit plugin I don’t care about ’cause I never used it but this other problem with ajaxSearch.js... I can’t have these problems on a professional site.

You may find my post offensive and for that I apologize. Please, understand that I’m not here to bash you or bash your ability to program. What I am here to do is state the obvious that I have found something that needs to be fixed and I’m betting these problems are because of incomplete code in the JS files.

Regardless of all that I must thank you and your team for their hard work in developing MODx and my GOD be with you.

LOL ... hardly offensive and actually appreciated since it reminded me of a plan for a contest. The JS is put in the templates for the demo content, hence my initial response. Should have more accurately stated "demo content". Thanks again.

@phpjunkie: did you solve the window undefined problem? I also get this when I try ajaxsearch on IE7; while FF all is ok...

I got different errors and yes I did fix both of the errors in my original post of this topic by commenting out the last line of the ajaxSearch.js file. The second error I fixed by disabling the QuickEdit Plugin. I never use it, I use the manager to edit articles/content so it was an easy fix. My site is simple but it is still undergoing construction. I used a different template then the embedded MODx template I was using.

My website: WePCRepair.com

http://modxcms.com/forums/index.php/topic,35917.msg217001.html#msg217001 solved it for me

Later I also had mistake with missing a </script> with FF does not need and IE stumbles upon

I don’t use apache or IIS. I like simplicity and both of them are far to complicated for any kind of simplicity. What you did is a workaround and what I did is a workaround and workarounds are not fixes to the code. The sad thing is, I don’t know javascript or I’d fix the code my self.