Re: Announcing Selling Made Simple - Open Source e-Commerce
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 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 -~--~~~~--~~--~--~---
Re: Announcing Selling Made Simple - Open Source e-Commerce
Basically what happens is you have a hierarchial content system. Unlimited subcategories, and products under these subcategories. When you create/edit a product you will specify a price, name, and description. (A name and description for each language if you have more than one turned on). In your product template you can decide how to layout the price, description, and product images. All products have the field template_id, so it is possible to in fact have multiple product templates. Not all sites will require this functionality, but it will definitely be handy for some. On Jul 27, 9:44 am, Dr. Tarique Sani [EMAIL PROTECTED] wrote: On 7/27/07, savagekabbage [EMAIL PROTECTED] wrote: The reason I wanted to go with database storage instead of flat file is because of the user who may want to have 20 different product templates for a large site. This just seemed easier to handle if the templates were stored in the database. I think you are mixing product details with templates here... or am i missing something T -- = Cheesecake-Photoblog:http://cheesecake-photoblog.org PHP for E-Biz:http://sanisoft.com = --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Announcing Selling Made Simple - Open Source e-Commerce
On 7/27/07, savagekabbage [EMAIL PROTECTED] wrote: The reason I wanted to go with database storage instead of flat file is because of the user who may want to have 20 different product templates for a large site. This just seemed easier to handle if the templates were stored in the database. I think you are mixing product details with templates here... or am i missing something T -- = Cheesecake-Photoblog: http://cheesecake-photoblog.org PHP for E-Biz: http://sanisoft.com = --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Announcing Selling Made Simple - Open Source e-Commerce
Hey guys, thanks for the feedback! I'm still not 100% sure im going to go database stored templates. Consider this: Right now there are three main 'content types': - Static Pages - Category Views - Product Views This means there will be a minimum of 4 templates if you include one for the outer 'shell' of the site. The reason I wanted to go with database storage instead of flat file is because of the user who may want to have 20 different product templates for a large site. This just seemed easier to handle if the templates were stored in the database. Speed shouldn't really be an issue as long as the templates area caching correctly. But yes, Dr. Tarique Sani, it will definitely make things more complicated. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Announcing Selling Made Simple - Open Source e-Commerce
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 -~--~~~~--~~--~--~---
Re: Announcing Selling Made Simple - Open Source e-Commerce
On 7/27/07, Jon Bennett [EMAIL PROTECTED] wrote: is it really so bad? why not save to the database, then use cake built in cache to speed things up? Why do you need to use a database to you cache? Besides I am not saying storing templates in database will slow down things - just make it more complex than needed. Tarique -- = Cheesecake-Photoblog: http://cheesecake-photoblog.org PHP for E-Biz: http://sanisoft.com = --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Announcing Selling Made Simple - Open Source e-Commerce
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 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 -~--~~~~--~~--~--~---
Re: Announcing Selling Made Simple - Open Source e-Commerce
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 ;) good points well made :) As only admins can CRUD templates, it will be fine for them to add view files. I was just writing loads of stuff about multiple domains and how that affects things, but then realised it doesn't affect anything at all! 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 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 -~--~~~~--~~--~--~---
Re: Announcing Selling Made Simple - Open Source e-Commerce
On 7/27/07, savagekabbage [EMAIL PROTECTED] wrote: Great to know about your new project 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... Looking forward to your alpha version Cheers Tarique -- = Cheesecake-Photoblog: http://cheesecake-photoblog.org PHP for E-Biz: http://sanisoft.com = --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Announcing Selling Made Simple - Open Source e-Commerce
This post is to announce a new CakePHP project, Selling Made Simple. Selling Made Simple (SMS) will be a fully functional, open source, e- commerce application. The main goal of the application is to be as simple to use as possible, while being highly extensible. But what about BakeSale? Why not just modify that instead? I'm taking a whole new approach towards SMS. I believe that there's nothing wrong with a cart having tons of features, as long as they are cleanly integrated. I also wanted to start off coding this using 1.2 instead of 1.1. SMS's main audience will not necessarily be CakePHP developers as all of the templates will be database stored. However, CakePHP developers should be able to easily write plugins for the system once it's completed. Our main audience is the average store owner who might not know Cake, or PHP. Modules Code Contributions will not require changes of core application files. An alpha version should be released mid August, but you can feel free to download the SVN version until then. Find more information at our website: http://sellingmadesimple.org --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
