OK, I can't be the only one who's been having a ridiculous amount of trouble with the site the past two days. I know Todd said that it was screwed up because of the time change (which I still don't understand because that's not until, like, April) but the site has been loading slow as hell and it's all screwed up. Half the time images won't load at all (like the images indicating new posts in a thread or forum) or the "quick reply" box will never show up. That or the site will just time out when Firefox is trying to load it. So...what's going on? Haha.
"because of the time change" I think that was a guess, as in not a definite reason for the problems. There's probably something on the host's end that's messed up. Maybe the SQL server went borked temporarily, or there's some scriptkiddies flooding the server, or one of the server's processes borked up causing other dependants to bork, etc. I honestly doubt it has anything to do with time changes. Just because the post times are off, doesn't mean it has to do with the time change, the servers just aren't sync'd properly.
The time change didn't mess anything up. The downtime today was a result of a RAID card in the server crapping out. Its fixed now. If you still have problems, its your computer
Your ISP's DNS server could be fucking up (which isn't unusual, actually). Not sure what I could suggest, really. I doubt clearing cache, etc, would do much.
Yeah. I do that at the end of every night. I just don't understand why parts of the LPA won't load (like the quick reply box, sometimes it just never loads) when other sites load perfectly fine.
Yeah. That's what I'm saying. It loads so slow that some things just never load. Oftentimes I'll get Firefox's "The page could not be loaded" page.
Yeah could someone perhaps give an insight as to why exactly the LPA is so slow lately and when it'll be fixed. If people are saying it's happening to them then it can't be the PCs themselves.
i get the following window when i click the image button in quick reply it works, but its wierd, and i bet not intentional
Um, thats completely normal Well, actually, it's not completely normal. It's there because IE7 is a worthless piece of shit and throws some worthless error message whenever the Javascript function prompt() is used, so the nice folks at vB worked very hard to create a workaround for a single browser that decides to throw all W3C and general usability standards out the window.
I agree with him. He's not bashing for fun. You average Joe's really don't understand it, but if you look at IE from a coder/designer's view [the people making the website for you to access it], it's a nightmare. Something will work fine in an alternative browser [to IE] that supports the standards that the W3C has set out, everything validates fully, and it display properly in all browsers ... except IE. That's where the headache comes in, and we lose sleep over finding countless hacks to get something working in IE without breaking the other standard-compliant browsers. I don't know what's taking the Internet Explorer team so long to get IE supporting standards [as the Gecko engine does], but fucking hell, IE7 was a disappointment that issues still weren't fixed. Also, the only browsers that pass the ACID2 test fully are Opera and an alpha branch of Firefox. IE fails miserably. Of course, end users never see the countless hours of sleep we lose, and still continue to use IE because they like it, and they don't care about standards and how hard we have to work. If you go see my website, you'll notice the dropdown menu I use for navigation works rather well in Firefox and other browsers. Explodes in IE. My site fully validates [minus the little meta bit at the top, blame Google], too. I've had enough, I'm off to bash IE for fun. /rant
i run and design code a site aswell...no issues so far with IE but yes, ive heard about all the issues with IE7...you dont need to explain it all out to me...its to be expected with early RCs from microsoft (issues such as this) my point is there is no need to always be like "IE sucks you noob!"...just say that it was the IE7 compatibility update in 3.6.5, no need for both of to write out explanations of why IE sucks, cause im sure most people already know about the issues with IE...saves us all time...aight? cool