First, you've got some race conditions in some of the mods you have installed. For example, the call to $.forumModuleEmotes is being made before the actual script that contains the plugin (/GuildFiles/258012/forum-mod-emote.js) appears on the page, so it's not loaded when the call to it is made. IE is pretty bad about not actually letting all referenced scripts on the page to load before reacting to the $(document).ready() function, but you can run across it in other browsers occasionally, too.

You can get a clearer picture if you hit F12 and navigate around your site. You'll see all kinds of errors being thrown. Mostly, IE will stop executing anything beyond an unhandled error, so the script that hides those forum groups on your forums page doesn't even get a chance to execute.

I've been fiddling with it for about three hours now, but I don't want to make a lot of sweeping changes that will break mod functionality for folks it's not broken for. I will go see if I can wrap your forum hiding script in a function and then call Sys.Application.add_load(function name here) to wrap it up so it doesn't actually execute until every resource on the page (CSS, external Javascript, etc) has fully loaded. Why IE doesn't wait to execute stuff in the $(document).ready() blocks is beyond me, but that's just how MS wrote it.

Wow! Thanks Aaron!

Hey, sure thing! I think the IE behavior of executing jQuery $(document).ready scripts before the document is actually ready (with all external scripts loaded, etc) is pretty new. Either a change in the browser itself or a result of me keeping GP up-to-date with the latest jQuery and MSAjax APIs (MSAjax is required for a lot of the controls -- though I wish Telerik had written them as server control wrappers around jQuery on the client-side, so that MSAjax wouldn't be necessary at all).

So given the following sample code, the way it was done before:


So if you take a look at the changes I made to that code, you'll see I just replaced the $(document).ready wrapper with a new one that contained the execution of the mod's script within a function, followed immediately after by adding the function to MSAjax's queue of functions to run after the page and all resources have loaded. The above code now looks like this:


So, it basically makes IE/MSAjax operate the way it should operate on doc ready. The good news, aside from the modifications necessary to existing mods and stuff  -- the GuildPortal scripts have had to be modified as well -- is that all of the other more well-behaved browsers will react to Sys.Application.add_load just as if it's $(document).ready.

Anybody familiar with MSAjax might wonder -- why not wrap the code in var pageLoad = function(), since that method gets called on page load correctly (after everything's fully loaded)? Well, thing is, you can only call pageLoad once on a page. After rendering and resource fetching is completed, IE/MSAjax, upon encountering the first pageLoad(), will faithfully execute the code within it, and then happily ignore anything afterwards that is also wrapped in the pageLoad() function. It's counter-intuitive to jQuery's $(document).ready, since with jQuery, you can wrap all the code you want in the ready handler, all over the page, and it will execute all of it.

So for MSAjax, add_load actually queues up all of the functions that have been passed to it throughout the rendering of the page, and then (internally) it calls pageLoad() itself, calling every function it was given. Why pageLoad() couldn't queue up without the developer having to explicitly telling it to is a mystery to me... Maybe if they open-source it I'll fix it for them.