Any Release for vBulletin 3.8????

[Akhil]

I recently upgraded to vBulletin 3.8 Beta. I wanted to run some maintenance, but the CMPS system refused to identity it saying:

vBadvanced CMPS Install
It appears that you are trying to install the vBulletin 3.6 version of vBadvanced CMPS on an older version of vBulletin.
Please go back to vbadvanced.com and download the version of vBadvanced CMPS that corresponds to your version of vBulletin, or upgrade to vBulletin 3.6 before proceeding.

Any help?

[KW802]

All of the vBa products will be updated accordingly when vB 3.8 is out of beta. While it is in beta, no official support can provided.

In the interim, you could try some of the un-official modifications that other vBa users have been doing such as this one (http://www.vbadvanced.com/forum/showthread.php?t=32014).

[Our Sponsors]

[jw0ollard]

Are you using the term "beta" loosely, or are we going to see a vBa release once 3.8 enters RC1? (Which will be next release?)

Frankly, I'm still peeved there hasn't already been, at the very least, a CMPS 3.x (3.5?) BETA release, for people like me who needed vBa working with vB 3.8 months ago. And it's fine if I don't receive an answer, but has anything that's changed since 3.8.0 Beta 1 actually had any potential ill effects on vBa??? My guess is no.

I obviously haven't looked at the inner workings of every single 3.8.0 Beta and compared notes, but I don't think there would even be much between 3.7.4 and 3.8.0 stopping vBa from working properly, save from the version check during the install script. I'm aware of some slight DB schema changes, and of course the new features in 3.8, but this is why I'm calling for a vBa beta.

For example, in my situation I've been waiting ever since 3.6.8 to begin a complete overhaul of my website. 3.7 comes along, I start gearing up for the overhaul, and what does vB do? Announces 3.8. So my predicament worsens. I'm not going to work for months at a complete website overhaul to have 3.8 released weeks later. So once 3.8.0 Beta 1 comes out I decide to at least start the initial coding, planning, etc. And then I find out there won't be a working vBa release for months to follow. Needless to say it put a grinding halt to my plans.

I will say the blame is all aimed at vBulletin, however... 3.8 was never supposed to happen. Kier himself answered my question directly, stating on the vBulletin forums for the first time (that I had seen) that there would be no 3.8 and that work would begin on 4.0.

So, Brian, I know you're mostly (see P.S. below) bound to vBulletin's release schedule, but with how minuscule the change between 3.7.4 and 3.8.0 actually is (I'd argue the smallest change in major revision history, and certainly less change than 3.6.x -> 3.7.x) can we at least hope to see a beta release soon after 3.8 enters RC1?? :)

I'm aware of modifying the install script, too, but it's not something I'm going to do, not due to potential instability/incompatibility between vBa/3.8 (I'm fairly confident the changes to vBa in regard to compatibility would be almost nil).. It's that I'm not going to work too much at rewriting parts of vBa and its modules to then have a major vBa revision on my doorstep with potential core rewrites, improvements, new modules, etc. And this is the same reason I'll be waiting to renew my other licenses for when we get ANY kind of release to work officially (beta or not) with 3.8.

And this has nothing to do with "support" or installing these things immediately onto a production site... I'm a developer and I at least need the means to TEST the next site revision or I can't do anything at all. So I'm really not understanding your "No official support" argument, Kevin... A Beta is almost always unsupported.. because it's a beta. :) But that doesn't mean we can't have that beta in the meantime.

The moral is that it's hurting us to not have access to a working beta, but it won't be hurting anybody to release said beta. So right now people like me are the only ones losing out. :/

And, I'll reiterate that with 3.8 entering RC, anything being changed between RCs (if there even is an RC2) would have almost zero likelihood of affecting even a "Gold" release of vBadvanced products. The code is nearly set in stone. So why no vBa Betas/RCs/Refreshes?

Thanks for hearing me out.. :)

=====

P.S. - I would just like to point out that the entire range of vBa products was updated on 12-18-2007 & 12-23-2007 to coincide with 3.7.0 Beta 2 & Beta 3, one of which was an RC (CMPS 3.0 RC2), 2 of which were refreshed again (CMPS "Gold" and Dyna 1.0.1, citing no further issues with the vB Betas/RC), and all of which were refreshed yet again to add support for the security tokens of vB 3.7 RC4.

That's 11 separate product refreshes during the vBulletin Beta/RC stage.. So why the sudden change in tune? :)

[Brian]

We've tried to keep up even with vB's beta versions in the past, but that hasn't always proven to be the best idea since (especially with vB 3.7) there were constant changes. We should be releasing a new version of each vBa product soon though that will include vB 3.8 support and at least a few new features or options.

[Our Sponsors]

[Infopro]

I've upgraded to 3.8 beta 3 and vbadvanced works fine here? What's not supposed to be working?

[KW802]

I've upgraded to 3.8 beta 3 and vbadvanced works fine here? What's not supposed to be working?If you search the forums, you can find various threads on the topic.

[jw0ollard]

We've tried to keep up even with vB's beta versions in the past, but that hasn't always proven to be the best idea since (especially with vB 3.7) there were constant changes. We should be releasing a new version of each vBa product soon though that will include vB 3.8 support and at least a few new features or options.

Thank you for responding.

I do understand your argument, but it's just kind of ironic that the move from 3.6 to 3.7 was absolutely rife with problems, mostly due to vBulletin not really knowing what they were doing, coupled with how unhappy the user base had become, considering it was "feature locked" before they even revealed it to us. Whereas at this point you could have probably just refreshed the 3 products with the few (if any) problems that popped up with 3.8, since the move from 3.7 to 3.8 was more a gimmick than any substantial change to the software. 3.8.0 really just should have been spread out among the minor revisions, and then I guess we wouldn't be having this conversation.

And if I didn't actually state the ironic part yet, it's that you probably shouldn't have bothered keeping up with 3.7 betas when you did, and you probably could have refreshed these (just once) during 3.8.0 Beta and not had to again until you were ready to roll out any major/minor revisions.

And now that there are only five Beta 4 bugs committed to RC1, we have an essentially final product, and still no means to run any vBa products.

So I will say again I understand why you may have decided to stop supporting Betas after the debacle that was 3.7 Beta, but I think that given what a gimmick 3.8 really is (minor revisions masked as a major one) that it just makes your decision seem sort of... Draconian. :)

..... But don't get me wrong though.. If I end up waiting all these months for more than just a refresh I'll still end up satisfied. But I think I'd probably need a major revision to CMPS and vBa Links (3.5 and 3.5?), for it to be justified considering how desperately I have been awaiting these new versions. :) I was thinking maybe Brian-sanctioned SEO support in CMPS 3.5?? *wink wink*

Thanks again.

[Brian]

And if I didn't actually state the ironic part yet, it's that you probably shouldn't have bothered keeping up with 3.7 betas when you did, and you probably could have refreshed these (just once) during 3.8.0 Beta and not had to again until you were ready to roll out any major/minor revisions.
Of course hindsight is always 20/20. After going through the 3.7 updates though, I was expecting a similar number of changes and issues with 3.8, which is why we decided to hold off on vBa releases a bit.