vBulletin 3.7.3 Released

**Brandon Sheley** · 08-26-2008, 02:25 PM

vBulletin 3.7.3

As promised last week, today sees the scheduled release of a maintenance version for vBulletin 3.7.x.

vBulletin 3.7.3 contains a number of bug fixes, details of which can be found in the bug tracker. Additionally, a change has been made to prevent users from setting their password to their username. See below for more information.

The security fixes included in vBulletin the 3.7.2 PL releases are also included in vBulletin 3.7.3.

Username=Password Disallowed

In this release, users will no longer be allowed to set their username and passwords to the same value. Users who already have a password that is the same as their username will be forced to change their password on their next login. Additionally, a tool has be added to the Admin Control Panel to email affected users with a new password. Please be aware of these potential compatibility changes when upgrading.

Upgrading from Previous Versions

3.7.3 is a maintenance release. We recommend that all customers running prior versions of vBulletin 3.7 upgrade to benefit from bug fixes and stability improvements.

Full instructions for upgrading vBulletin are available here.

PHP and MySQL Requirements

Please note that vBulletin 3.7.x requires at least PHP 4.3.3 and MySQL 4.0.16 or later.

However, we recommend that vBulletin 3.7.x is run on PHP 5.2.6 with APC (or a similar opcode cache) and MySQL 5.0.51 for best performance and stability.

End of Life for PHP 4

PHP 4 has now reached its end of life. We strongly recommend that customers update their servers to PHP 5.2.6 if they are still running PHP 4. vBulletin 3.7.x supports PHP 5 without any problems, though you may need to disable strict mode for MySQL, see here on how to enable 'force_sql_mode'.

Note: We will continue to support PHP 4 in the vBulletin 3 series.

Download vBulletin 3.7.3

As usual, vBulletin 3.7.3 is available for all customers with valid, active licenses to download from the vBulletin Members' Area.

vBulletin Members Area

vBulletin 3.7.3 Released - vBulletin Community Forum

**Caddyman** · 08-26-2008, 02:34 PM

cool, i installed a forum, fresh last night, and now i should upgrade?

I THINK NOT.

i guess the username/pw the same disallow is purely for security purposes?

**magz** · 08-26-2008, 02:37 PM

Just upgraded to 3.7.3, all went without issue.

Though i must admit, each time i upgrade, I always hold my breath wating for a dreaded error message during install lol

So far, so good

**Soliloquy** · 08-26-2008, 03:48 PM

I guess no improvements on the user albums yet, huh? My members are already asking why they can't do stuff...

**snakeair** · 08-26-2008, 06:00 PM

Quote:

Originally Posted by magz

Just upgraded to 3.7.3, all went without issue.

Though i must admit, each time i upgrade, I always hold my breath wating for a dreaded error message during install lol

So far, so good

I do the same thing each time when i upgrade.

On this upgrade, i forgot to do a backup before starting but the upgrade went threw fine.

My last backup done was on Saturday if i needed it.

I'm pretty sure most members do use the there username as there password. But it's a nice security feature anyways.

**FoxyWL** · 08-27-2008, 10:24 AM

i had 116 members using the same user and pass! didn't think i would have that many, upgrade went smoothly and emails sent to affected members

**Soliloquy** · 08-27-2008, 11:07 AM

Wow Foxy, that sure seems like a lot. How many members do you have? I'd never have guessed it be that high.

**Brandon Sheley** · 08-27-2008, 11:09 AM

I guess we had about 100 as well, I didn't see them when I ran the search, but Mike said he did.

**snakeair** · 08-27-2008, 03:12 PM

I had 24 out of 1800

Even that number is a shock to me.

**Brandon Sheley** · 08-27-2008, 03:16 PM

I was talking with someone the other night, and we were thinking it was the spam bots maybe?

**snakeair** · 08-27-2008, 03:22 PM

That could be it. But i thought the automatic bot's code didn't work to well with vbulletin. I know it works well with phpbb forum's.

Hey, let's just ban all those usernames. (Just kidding, could be a loyal member)