The reason hacks for betas are generally not allowed is because, guess what, it's a beta! Betas are released to test code, and installing hacks compromises that objective. You can install hacks on a beta, you can even make a hack site for it, but you probably won't find hacks for betas here.

Have at it. Nobody will stop you.
I dont see that happening. That is your opinion and you have every right to feel that way.
And nobody is stopping them. VB.ORG just doesnt want them distributed here. And that is their right, as it is their site.

I still have no idea why people are getting bent over a product that isnt even available in the Beta stage yet.. :ermm:

Well, I'm not a coder, I'm a hack installer (aka Greedy User of Other Peoples Work.). And I think I like the idea of not having all sorts of stuff floating around berfore the final product is even available.

I also like the idea of a strict line being drawn between simple "Plugin" type hacks and those that require code changes. After all, the plugin idea is to make repair/restore after damage easier, and to make upgrades less painfull. I definately want to know before I get all hyped up about a new hack whether or not it will be a code changer.

Just my 2 pennies.

while yes it should be upto the coder/installee what s/he installs and on what product, you have to remember that this is infact an official jelsoft board despite the fact that no one get's paid or even donations every once in a while (speculation). you can understand that jelsoft may want to discourage users from hacking beta boards, even if like me you're not in disagreement, my personal opinion is that given more time/less lazyness jelsoft would've reskinned but even that is open to debate given just how much can you do and retain ease of customisation?

while this place has many up's and down's and beleive me despite being a regular theirs certain things i think are ++++e, i do beleive we have the right administration team in place, our issues are listened to and commented on, our problems are remedied in most cases and the production rate of hacks is above all expectation given that the coders don't actually get anything in return, please don't blanket the whole site with your discontent at the fault of one or two features/members/staff/etc.

the site is what you make it, whether that's posting, supporting the hackers by installing their scripts and commenting on them or just posting in the lounge, it's a site that is as good as the effort you put in. :)

Jelsoft, in all their announcements about 3.5, tell us it will be easier to hack, and they will provide more plugin spots as they are required. Please tell be how they intend to test/prove the first, and provide the second, in the beta stage, if no hacks are allowed to try it ....... :)

if jelsoft were commited to this community the way they should be, they would've made a similar announcement over here which was geared towards the hack community, i mean geez we found out that it was gonna be OOP based from a fan site over this one, i beleive Wayne should be the one talking to Kier telling him that he should put the effort in over here though it's yet to happen, as you said with all of their plans for 3.5 who's gonna be the ones providing the additionals for their customers, us! yet we're yet to receive a single official word regarding 3.5 over here :(

To clear things up for people who don't seem to understand or is new to vBulletin.

Before vBulletin 3 wasn't even out we had hacks for vBulletin 2. Then vBulletin 3 BETA was out, but the rule for hackers was there will not be any hacks released while vBulletin 3 BETA was still in the BETA stages. The reason this was done was because alot of code changes happen durring any BETA stages of any software. Once vBulletin 3 was GOLD. Hacks where allowed to be submitted here at vBulletin.org because it was out of the beta stages. And any updates afterwards didn't change much code.

Same thing will prolly happen here for vBulletin 3.5. While vBulletin 3.5 is still in the BETA stages, you will most likey not be allowed to release any hacks untill vBulletin 3.5 is out of its BETA stage. I'm sure once vBulletin 3.5 is out of BETA. vBulletin.org will open new forums just for vBulletin 3.5 so things will be organized. Hope this clears things up. I'm not saying this will indeed happen, but im pretty sure this is the way things will go as they went in the past.

Also Sabret00the has some good points. Jelsoft should put more effort into vB.org. But thats another thread. ;)

Ever think they are using said hooks themselves, otherwise why add them to the source right? Lets be honest here, they did not add this new stuff just for the hacking community, do you honestly think they will release code without testing it themselves? :)

Not allowing hacks here hurts no one, and prevents more problems then it causes. No one is telling you that you can't hack your own copy of 3.5 beta when it comes out, I'm sure most of the guys around here will be doing so as will I.

The problem with allowing hacks in a beta period are,

1) The public beta is meant to test the new code on a wide scale, allowing people to hack the source may result in many bogus bug reports at vBulletin.com

2) In the beta stages the code will change more often then it does in the 'gold' or 'final' stage.

3) Beta's are for testing, not for boards running in public space (although many run them in public space anyway).

(Again this is not 'set in stone')

Testing the code themselves is what they do pre beta. Surely the point of a beta is for others to test it. If they didn't add these hooks just for the 'hacking' community then who else did they add them for ? Jelsoft don't need hooks to make changes, they just edit the source.

Allowing them doesn't hurt anyone either. :) Remember that not all hacks are complicated and require lots of code changes. I'm quite sure some will slip very easily into the initially provided hooks.

These are all very nice arguments, but none seem very convincing for actively refusing to host 3.5 hacks while it is beta. You simply have to stipulate that any bug must be shown to exist on an unhacked board, or it will be considered unconfirmed.

Yes, beta's are for testing, and code will change - and 3.5 hacks would be exactly the same - need testing and the code in them may need to change. Surely it is the coders choice as to whether they want to be involved in the extra effort this may entail, and board owners choice as to whether they want to be involved in the extra effort to update any they test/install.

People will start working on new hacks, and existing conversions, as soon as 3.5 is out, and they are going to want others to test their code. If you refuse to allow these people to host them here then they will simply go elsewhere. A loss to the vb.org community. As a side effect these hacks will then also become more readily available to all the 'less honest' boards as well, since no one else has a registration check system.

Anyway, I'm obviously banging my head against the old brick, so I'll say no more on the matter, I have made my points. :)

That's the main reason why when vB3 was in beta we did not allow vB3 hacks posted here at vB.org.