On Jul 27, 12:10 pm, "Jon Bennett" <[EMAIL PROTECTED]> wrote:
> > > SMS's main audience will not necessarily be CakePHP developers as all
> > > of the templates will be database stored.
>
> > I don't get the connection between the two - if you are storing the
> > templates in database just so that they can be easily editable by users I
> > would say please think again... the added complexity is not worth the
> > feature added, also it makes it difficult for the theme designers to work on
> > templates (i do presume you will have themes?)
>
> > If you really want web based editing - take the approach which some popular
> > CMSs take - read and write to files...
>
> is it really so bad? why not save to the database, then use cake built
> in cache to speed things up?
>
> I ask as I have a project that requires similar functionality and that
> was how I was intending to do it.
Using cache to mitigate the cost/need to read views/templates from the
db, which are only there so that you can 'easily' edit them seems like
a weird circular dependency to me.
It would be a lot simpler to edit the view/template file via a form
(did that for myself before for small changes when without ftp
access). Choosing a (user defined?) layout file based on some logic/
user preferences, rather than retrieving a layout from the db would
simply be "simpler".
If you go the db route, I hope some defensive coding is used so the
"problem connecting to db" & "problem with layouts/views table" error
messages still display ;)
my 2p.
AD
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
