> > 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. jb -- jon bennett t: +44 (0) 1225 341 039 w: http://www.jben.net/ iChat (AIM): jbendotnet Skype: jon-bennett --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
