vB3 hacks

[Fusion]

I realize this may be like spitting into the wind, but nothing ventured...

Have you considered implementing some form of template-based hacks in vB3? I'm thinking modifications to the .php files can be entered through the Admin CP, and if it's an initial change, the original file can be saved in the database. While this might increase the database somewhat, I'm just talking storing the original file, not some CVS-tree of hack-changes. The idea is to allow for modifications while easing the posibility to revert to the original aswell as making copies of the files, all from within vB.

Am I asking too much?

[tubedogg]

I think so.

The problem with that is twofold. First, it would increase the size of the database as you mentioned. In addition it would require files to be CHMODed 777. Also it would encourage people who have no business hacking, to do so. Not that people shouldn't hack but unless you are at least familiar with vB and know some PHP/MySQL you should not be hacking. That kind of system would encourage users who don't really know much about it to try hacking and when it doesn't work, up shoots the support ticket rate.

And secondly, this would give the implication that we support hacked boards, which we cannot and do not.

[Fusion]

Somehow I sense that #2 weigh in far heavier than #1. ;)
You do realize with todays system people are.. well, not so much encouraged, as left to their own devices when implementing fixes to bugs as found in the Bugs forum.

As for being a potentional risk with regards to permissions, and suggesting it's "okay" to meddle with the files, I don't quite see how this would be any different than it is today. Files will always be at risk from inept users, regardless of their permissions. At the very least with this in use there'd be onsite backups as a failsafe.

Maybe a poll would be helpfull to see how "safe" it really is today.