hope that is all the problem is.
We aim to release 5.2.0 at the same time as WP release 3.5 – so very, very soon now.

I had the same problems as Jennie Chancey. Now I deactivated The “Thank You for Post” Plugin and all works fine with the internet explorer (7-9). 

Really? You were getting these odd messages?

Jennie Chancey said
I disabled the plugin, but it didn’t help. She still gets a “slow-loading script” error message. IE8 users aren’t having this issue–only this gal on IE9. And it only happens when she logs in and tries to go deeper in the forum (past the first opening page). She can’t view threads or post.

Thanks for checking into this!

Cheers,

Jennie

First I didn’t believe my users, cause when I looked at the forum with IE everything looked fine. Than yesterday I got a mail, in which a user asked my how to make a post in the new forum and how to read threads and I decided to look at the IE again. Everything works well, when you are not logged in, when you are logged in, you only can see the first page normal, if you go deeper there is no layout anymore tony text.

I deactivated all plugins and after I deactivated the thank you for your post plugin everything looked fine.

Ah – Ok – so this could be the CSS loading issue with IE. SO all being well this will be fixed in the next update due to be released with WP 3.5 (which is supposed to be today!)

FWIW, I don’t have the “thank-you for posting” plugin installed at all. My user is on IE9 and still has the problem of nothing showing up beyond the first page of the forum.

Thanks for the help!

Jennie

well, its not related to any specific plugin… but IE has a stupid limit of 32 css files…  so anything, wp theme, wp plugin, sp plugin, etc that causes you to go over 32 css files will cause the problem…

WP just announced they are delaying the 3.5 release until Monday…  so looks like Monday evening for the 5.2 release…

I can happily report that the new versions of WordPress and Simple:Press have solved my issue with logged-in users viewing any forum page beyond the first on Internet Explorer.  It appears that indeed it was as a result of having too many css files loaded for IE to handle.

Now that IS excellent news and I thank you for the update.