[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Template storage mechanism?

The template storage mechanism is just a full template file goes into a single field? (or is there a more complex disassembly into fields)


Les Richardson

On Fri, 6 Apr 2007, Christopher Murtagh wrote:

On 3/25/07, Chris Travers <..hidden..> wrote:
1)  There is some debate (so far, over IRC) over whether to move
templates into the database,
  a)  makes for easier security because we can have full ACL-based support
  a)  makes it harder to edit using a basic text editor.
  b)  adds one more area to the code that will require more extensive testing

Any other thoughts or concerns?  What do people think about this
direction in general?

I'm all for it. Everything that is outside of svn should be in the DB
IMO, because it's not code, it's data. It's fairly trivial to have a
mechanism that provides for admins to click on a link to download a
template and then use a file upload (via a web form) to replace it. It
means that they still get all the functionality of their favorite text
editor, *and* their templates are backed up with their data.



Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
Ledger-smb-devel mailing list