[eluser]Tookings[/eluser]
This may be answered somewhere...but I couldn't find it. Feel free to tell me to search better.
Has any done or developed anything to store views (well, really view templates) in a database?
I usually end up writing my own lightweight template systems for very customized applications -- and in CodeIgnitor I use two views together, one is a fairly generic "template loader" view with PHP code that calls parse() on a second HTML-only view "template".
However...for multi-domain sites managed from one master location (many duplicated identical public codebases, with one admin codebase) other than 1 or 2 values in a config file, I keep everything in one database and all the code completely generic between the sites. Once a change on the QA code is ready, a script pushes new code out to all the sites at once. This works well -- but designers updating the base templates need an easier way to modify them without pushing out multiple files or even needing FTP access.
Just curious if anyone had already done this...I'll probably just modify the parse function to load templates from a table instead of views. (Since the designers don't need access to the PHP template loader view.) But I was curious if anyone had redone ALL view functions to pull their code/content from tables? And...if so, why?
Or if this was a terrible idea. I haven't slept in a 30 hours or so.
Thanks!