I will be upgrading us to the latest vbulletin software (3.0.10) this evening when peak users die down. There is not much to this patch other than security fixes and such. It shouldnt take more than 10 minutes to upgrade, and then we'll all be back on our merry ol' ways. Cheers,
Alright, expect it tonight. Tech won last night and thus I was incappable of using my computer to update (camping out for UGA tix).
We're up and running on v3.0.10. I'm tired, and going to bed. A bug was fixed in Firefox 1.5 that causes the menu positions in the WYSIWYG editor to be incorrect. This has been fixed in vBulletin 3.0.10 for these newer versions. The vbulletin_wysiwyg.js is compatible with 3.0.2+, it is therefore recommended you upload this file if you intend just to patch your current install. The original purpose of this release was to provide a regular, scheduled bug-fix / service release for the new 3.5.x series, but newly discovered flaws in Internet Explorer and PHP have necessitated a security release for all three vBulletin branches. The first flaw is in Microsoft Internet Explorer. It affects vBulletin image uploads and potentially opens a cross-site-scripting exploit. It has affected many web-based applications that allow image uploads, including phpBB and Hotmail. Although a fix from Microsoft would be preferable, we have implemented a work-around in all three branches of vBulletin to prevent the Internet Explorer flaw from being exploited. The second flaw is in PHP and may allow the entry of unsanitized data into several areas in vBulletin. This may create security holes that are not directly caused by vBulletin, simply exploited through vBulletin as it uses affected PHP code. PHP 4.4.1 has been released to address this issue (no updated PHP5 is available yet). If you are running PHP 4, it is strongly recommended that you update your PHP installation to 4.4.1! I'd just like to reiterate that neither of these flaws are directly related to vBulletin. Rather, they are flaws in software that ties into vBulletin. We are simply creating workarounds for these issues to prevent them from being exploited.
security issues aside, the header is looking very seasonal the logo looks like it's had a little bit of the viagra too
yep, decided to boost it a bit Im somewhat dissapointed though in the results of comprimising quality in order to have a reasonably sized image.
Im working on this, I didnt forsee those being affected by the patch and will be working this week to get it all back up.