hehehe you're right ;)

I would not use this, you know why?? if not, let me give you one answer, it takes up more space then the database does, I like it running it off the database, doesn't take up as much space then the actuly HTML type of docs does......and it's easyer to use just by going thru. the admin CP :)

It takes the same amount of space (and I actually think it takes more in the database, with the MySQL table and its indexes). The only difference is under which category of space it is (file system or database).

I wouldnt use it.

I prefer to keep all the templates in one place within vBulletin. I do think that the template backup system should be incorporated into the official release of vBulletin - it's a great addition.

Hmm, won't use it too...

It would be a good option, I'm sure some people will find it useful. In my personal opinion, I wouldn't use it.

I'd use it gladly. :)

bumps :p
I would :)

Great idea, getting templates from files should be faster then db in most cases. In addition, some may like to edit all their templates at once then upload it all at once when it's done. Currently, that can be accomplished by installing vb on your localhost, but not every designer wants to be running apache, php, and mysql on the machine he or she uses for design.

The only bad part is it it's *slightly* harder to write a template editor page for file stored templates then database stored ones.

And firefly is correct about the space. It indeed takes less space having text stored in files then in a database.