[NOT ALLOWED] Where are we supposed to post 3.0 hacks?
 

I figure this time as I do some of the stuff I will post it as I go, some of the stuff I do is just to involved for me to begin to write up instructions (like my CMS) but the smaller simple ones I will post this time.

Just wanted to know where to post the stuff, put this ten second one in the beta under 2.3 as there was not 3.0 option.

Please don't post them yet as the forum structure is not designed to accomodate them.

If you read any of the announcements, you're not supposed to post ANY vBulletin 3.0.0 hacks as the software is still in beta stage. The developers will have a helluva time bug testing for public betas if everyone's hacking them already. vBulletin.org has stated in a couple different instances that 3.0 hacks are not allowed here until the software goes gold.

Or possibly as a few of the admins/mods have said, a more stable/finalised RC is released. :)

You're wokring on a CMS? Me too, maybe we could write it together?! Vb.com support will release they're CMS only about year 2005 ... and beyond :glasses:

IMO not allowing hacks is redundant.

people going to Jelsoft because of problems might have hacked the boards anyway.

it's not hard for a team member to ask if they've hacked the board when someone comes with a unique issue. At least allowing a beta hack section, with a disclaimer that if they encounter any bugs to uninstall the hacks to see if the problem persists doesn't seem that difficult to me.

:ermm:

@heretic: it's not the users we want to pretend, it's to make the devs work of bughunting easier.

you can't say they should ask before every bugreport if the users has installed a hack....

I agree...

vB3 beta 3 has enough bug problems on its own, without any being caused by hacks - You can analyse the code, and perform whatever code changes to your own board that you want, but before reporting any bugs you find, make sure you test it on an un-hacked board first...

Satan