vBulletin 3.6 Beta 1 Released

Jesoft announced the release of vBulletin 3.6 Beta 1. vBulletin 3.6 Beta 1 is available for all licensed customers to download from the Members' Area now.

vBulletin 3.6 contains a large number of new features, many of which have been included as a direct result of customer feedback.

This code has been running well on vBulletin.com for the past week, so we are confident that the code is robust and relatively free of problems, but customers should bear in mind that this is a public beta, not a certified 'stable' release so the following caveats apply:
Beta software is unsupported and you install beta versions at your own risk.
Some minor bugs remain unresolved at this time, so beta software should not be on production sites.
You should always back up your database fully before attempting to install beta software.
If you choose to install this version, you should be aware that we plan to release new beta versions in rapid succession as bugs are fixed and holes are plugged. Do not install this beta version if you are not willing or able to keep up-to-date with new releases.
The ImpEx import system does not support the 3.6 code yet, and will not support it until the release of 3.6.0 (stable).Installation / Upgrade
If you are accustomed to the install and upgrade procedure used by vBulletin 3.5 then the 3.6 install and upgrade process will be familiar to you.

Hacking / Plugins
While there have not been extensive changes to the underlying architecture of vBulletin 3.6 from 3.5, it is possible that certain hooks may have changed. Therefore you should check with the author of whatever plugins and products to attach to your vBulletin installation to inquire about their compatibility with vBulletin 3.6. Plugin authors should be assured that we do not anticipate major code changes between the Beta 1 code and the final 3.6.0 code, so plugins written for or adapted to 3.6 compatibility should still work with the final code.

Javascript / AJAX Problems
Many of the Javascript files for vBulletin 3.6 have changed. However, if templates are reverted or adapted correctly there should be no issue with cached old Javascript files, as we have implemented a system that should force clients to reload Javascript files after an upgrade. If you discover what you believe to be a Javascript problem, please ensure that you are not using cached files by doing a ctrl+F5 hard refresh before reporting it as a bug.

I installed it to a test forum this evening. One thing I recommend is, if you're going to install it to a copy of your existing datebase you need to turn off the hook system. After installing to the test forum, I got multiple error messages, all having to do with hacks and modifications, and wouldn't even allow me to enter the acp to disable the hooks system. Thankfully, noppid was online and had a fix for me. Thanks again darlin'.

Now I'm going through the acp trying to find where to turn on the multiple quotes feature.

Oh and I found one hack that can be uninstalled... the Automatic Welcome PM. They integrated it into this version :D

hmmmm... from the forumhome page, when I click on a thread in the Last Post column, I'm getting

No Thread specified. If you followed a valid link, please notify the administrator

Odd...

hmmmm... from the forumhome page, when I click on a thread in the Last Post column, I'm getting

No Thread specified. If you followed a valid link, please notify the administrator

Odd...


huh?

LOL... Mike at vb.com said I didn't follow the last step of the upgrade instructions... You didn't run update thread counters and then update forum counters like mentioned in the last step of the upgrade

However... that wasn't IN the upgrade instructions, and I can't find where to do it at


EDIT... all fixed and working like a charm!

LOL... Mike at vb.com said I didn't follow the last step of the upgrade instructions...

However... that wasn't IN the upgrade instructions, and I can't find where to do it at


EDIT... all fixed and working like a charm!

Actually there is a note to perform those counter updates during the upgrade process about 7 steps before the upgrade finishes. It's hard to catch. But I got lucky.

Just finished grabbing a snapshot of my production database and will begin playing with the beta today... thinking it might be fun to attempt to use the primary and secondary database feature and see what kind of performance hits vB takes overall.

Actually there is a note to perform those counter updates during the upgrade process about 7 steps before the upgrade finishes. It's hard to catch. But I got lucky.


LOL... there may be, however, my upgrade only got to step 5, then took me to the acp to login. Mike was talking to me about step 7, and 11 and whatever... I'm like WHOA wait a sec.... mine never went past step 5!

They're going to look into a possible upgrade bug

I also had to remove most of my hacks. GOOD thing it's only a test forum

scary :(

I wont be updating locoforum for a few weeks I'm sure.

Naw not so scary. Coders are already working on porting their hacks to 3.6... take a look on .org. Anyway, the bugs have been minor ones, and have been taken care of asap. I'm impressed, but then it doesn't take much to impress me ;)

Quite a few of the "bugs" reported on .com have, in fact, been user-error, as usual.

I have a feeling it won't take nearly as long for 3.6 to go gold, as it did for 3.5

I use the computer help forum database for testing my hacks. I used that database to test vB3.6. It all seems to work fine. :)

I'll be waiting for Gold myself...3.5 betas were a pain until about beta 3