I'm periodically finding script errors in the past day or so when I post or reply... it may be parsing the bbcode since it is worse if I use a lot of quotes or formatting...
Have you tried clearing your browser cache and rebooting? I had the same issue when the last upgrade went online. I used Norton Utilities (Windoctor and CleanSweep), then rebooted and all was well...
Yes. Even tried deleting the digitalpoint cookies. It seems it's okay for simple posts without bbcode formatting - not sure what bbcodes create the problem yet.
IE6 on XP -- and I don't LIKE using the other one, personally. More info: When it happens, it doesn't matter whether I'm using the Quick Reply or the regular reply mode. However, if I'm using Quick Reply, when the problem occurs, the little black "Posting..." message doesn't appear. When it happens, the page hangs but if I just leave it to sit, eventually an IE error message box pops up informing me that "a script on the page is cusing IE to run slowly" and asking me if I want to abort the script -- I say "yes" and the message posts fine. Other times, the page doesn't hang but I get that little yellow "Done with script errors" icon in the lower left of the IE screen.
I does sound like a bug. The good news is, the vBulletin developers are working quickly to get rid of the bugs, and in fact the vBulletin.com website is already running the next version, Beta 3. So there's a good chance the fix will happen soon.
Weird - I had pretty much the same problem with IE but I guess I didn't wait long enough for the "slow script" dialogue before forcing the browser window closed. I was right in the middle of schooling noppid on that content vs marketing issue, and it was really crimping my style. So, I opened FireFox (which I don't like either but I keep it around to check my site for FF issues) and used it to post. That's when I received the "slow script" dialogue and was able to abort it and get the posts in. The problem went away after that though, which I assumed was due to the cache cleaning, Windoctor, or reboot. Hmmm...
In the works of the late great Dale Earnhardt, "It does't matter what they're saying about ya, as long as they're talking about ya." That was actually a good debate. I learned a thing or two.
I already tried the cache cleaning, cookie deleting, and reboot. I haven't tried registry scraping yet, though... or noppid smacking...
But it is sort of your department... if noppid smacking is the only way, that's the way we'll have to go... I have this image of the Monty Python fish-slapping dance...
What about Norton WinDoctor? When I ran it, it found some ActiveX issues and cleaned them up - that could have been it. That won't work - it has to be a human sacrifice...
Yes, Windoctor is the "registry scraping" I was referring to... I'll do that in a minute. I don't know if we want to sacrifice Brother Nop though... he might come in handy. What if we just smack him around a bit and have him yell a lot so the codebug gods THINK we're sacrificing him?
I think it may be some AJAX bugs that were fixed in beta 3. I haven't experienced them myself, but I did see a reported bug that sounds like it was it that was fixed.
Here's an example of a reply with bbcode that caused the board to hang in IE6 - note the nested quote... I wonder if that could be the problem? http://forums.digitalpoint.com/showthread.php?p=217635&posted=1#post217635
Update: I just tried a similar reply but in this case I didn't use a nested quote -- instead, I put the inner quote above as a separate quote and it posted immediately -- no hang. I think the bug is in there somewhere.