vBulletin 3.7.1 Released

werd... vb sucks. lol

good luck fixing it on your own.

I'm adding to the fun of the upgrade, just found a problem at VB on the bug tracker which is also an upgrade I have on my forums

But mine works, just don't show updated bug reports like the rest of the forum.

And another forum that has troubles with a web page is here. The tags page is having a bit of a bad day

Problem solved
Browser cache needed clearing for some strange reason

I upgraded. No offense though, but it's been in a pain in the ass recently to keep upgrading vBulletin. It's great that they're finding bugs and fixing them, but I'd rather them find them all first.

I went from 3.6.8 to 3.6.9 to 3.6.10 to 3.7 and now to 3.7.1 in such a short period of time. I also have custom skins that keep getting messed up and it's money out of my pocket to continuously have them fixed/upgraded. :(

My skin was fine with 3.7 now I am having a submenu display problem (JS menu) with 3.7.1 for some reason..

Originally Posted by EGS

I upgraded. No offense though, but it's been in a pain in the ass recently to keep upgrading vBulletin. It's great that they're finding bugs and fixing them, but I'd rather them find them all first.

I went from 3.6.8 to 3.6.9 to 3.6.10 to 3.7 and now to 3.7.1 in such a short period of time. I also have custom skins that keep getting messed up and it's money out of my pocket to continuously have them fixed/upgraded. :(

My skin was fine with 3.7 now I am having a submenu display problem (JS menu) with 3.7.1 for some reason..

As this was only to fix bugs, you could have waited for the next release or the release after that to wait for more bug fixes to have been found. (only in security releases should you upgrade asap)

ps. they will never find all the bugs, its a continuous on going thing, so just choose when it is a good time to upgrade when you feel there has been enough bugs found to warrant an upgrade for you.

The latest bug fix IMO was a good one with being able to kill certain tag words dead.

One of my biggest bug bears has been the scum that post Nokia, Viagra type posts. You kill their post then find a shed load of their tags sitting un noticed.

The browser cache problems caught me out though

I think i'll stay with 3.6.x for some months more.

I have too many customised templates, and
it would take a whole lot of time to update them to 3.7.x accordingly.

oh man I just installed 3.7.0 and now theres another 3.7.1...

Anyone else thinking IPB is looking better and better now? Seems vBulletin are taking a IPB step with the developer blog and letting everyone know about updates just how IPB have started doing

I never knew that -- if that's the case, Jelsoft really need to come up with their own ideas.

IPB are not the only ones that do that, plus it is something which was requested by many.

I'm aware of that its just vBulletin is in direct competition with IPB as such being it the main paid for BB software as opposed to vBulletin so everything is compared between the two and IPB has been doing this for quite a while. Especially the developer's blog.

Originally Posted by hornstar6969

IPB are not the only ones that do that, plus it is something which was requested by many.

The important part is the bad business management. They made a decision in past to enable blogs for vb customers , now they reverted that discussion and followed IPB's route.

Anyone knows vbeo work on PHP 5.2.6 with APC (or a similar opcode cache) and MySQL 5.0.51 ?

Yes, it does. We have PHP5.2.6/XCache/MySQL5.0.51 here on vbseo.com.

Originally Posted by Mert Gökçeimam

The important part is the bad business management. They made a decision in past to enable blogs for vb customers , now they reverted that discussion and followed IPB's route.

Your right, they have managed things poorly, they didnt think of a clear business path to take. Hopefully development will continue on the blogs and it wont become stagnant because only vb are using them.

However it was important for the community to use the vb blogs, so bugs could be found, and the people had a chance to use and test them before buying them. Now that has been done, they promised to make communication clearer since vb 3.7 being released they chose to use their own blogs to do this communication through. It has its pluses and minuses, some will like, others wont.

I feel instead of deleting the blogs, they should move all the blogs to a vb blog archive in the forums (a feature which has been requested many times is just that, being able to move blogs to the forums, and posts in the forums to the blogs)

Overall, I wont be switching to any other forum board any time soon.