I would tend to agree with AD and Tarique. Storing template in a database which would then be cached as files, does seem crazy.
However, I would also point out that allowing public editing of views (stored in a database, or a file system) seems to be asking for trouble. I would put some pretty heavy sanitization on it, given the flexibility of, say, an eval command in a posted template. Of course you could get around this problem by just storing template parameters in a database (eg. colour of headline) and then having one fixed view which included all these as parameters. Is this what you mean by templates in the database? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
