Re: Front-end for end-users and admins design
Thank you for enlightening me. I'll do some more reading and come back with questions, most probably :) On Wed, May 19, 2010 at 8:51 PM, calvin wrote: > Due to the reasons explained by WebbedIT, the best thing to do is just > use admin routing. At the minimum, the models used by your admin and > end-user "apps" are going to be nearly identical, if not the behaviors/ > views/elements/helper/controllers/components as well. So it just > doesn't make sense building two separate applications, especially when > Cake makes it so easy to build a separate admin area with Auth and > admin routing. > > On May 19, 3:55 am, WebbedIT wrote: > > I am currently developing a large app which needed an area for the > > site owner to administrate the site, another area for organisations to > > administer their content and an area for standard site users to > > register and maintain their profiles. > > > > At first I thought it was sensible to do 3 apps on seperate sub- > > domains but you soon realise that you end up duplicating a lot of code > > and when you make a structural or cosmetic change it becomes a lot > > more work to replicate it across the 3 sites. Didn;t take me too long > > to integrate all 3 sites into the one app and it's so much better now. > > > > My vote, use routing or whatever other method you want but keep it all > > in the same app. > > > > HTH > > > > Paul. > > > > Check out the new CakePHP Questions sitehttp://cakeqs.organd help others > with their CakePHP related questions. > > > > You received this message because you are subscribed to the Google Groups > "CakePHP" group. > > To post to this group, send email to cake-php@googlegroups.com > > To unsubscribe from this group, send email to > > cake-php+unsubscr...@googlegroups.comFor > > more options, visit this group athttp:// > groups.google.com/group/cake-php?hl=en > > Check out the new CakePHP Questions site http://cakeqs.org and help others > with their CakePHP related questions. > > You received this message because you are subscribed to the Google Groups > "CakePHP" group. > To post to this group, send email to cake-php@googlegroups.com > To unsubscribe from this group, send email to > cake-php+unsubscr...@googlegroups.comFor > more options, visit this group at > http://groups.google.com/group/cake-php?hl=en > Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Re: Front-end for end-users and admins design
Due to the reasons explained by WebbedIT, the best thing to do is just use admin routing. At the minimum, the models used by your admin and end-user "apps" are going to be nearly identical, if not the behaviors/ views/elements/helper/controllers/components as well. So it just doesn't make sense building two separate applications, especially when Cake makes it so easy to build a separate admin area with Auth and admin routing. On May 19, 3:55 am, WebbedIT wrote: > I am currently developing a large app which needed an area for the > site owner to administrate the site, another area for organisations to > administer their content and an area for standard site users to > register and maintain their profiles. > > At first I thought it was sensible to do 3 apps on seperate sub- > domains but you soon realise that you end up duplicating a lot of code > and when you make a structural or cosmetic change it becomes a lot > more work to replicate it across the 3 sites. Didn;t take me too long > to integrate all 3 sites into the one app and it's so much better now. > > My vote, use routing or whatever other method you want but keep it all > in the same app. > > HTH > > Paul. > > Check out the new CakePHP Questions sitehttp://cakeqs.organd help others with > their CakePHP related questions. > > You received this message because you are subscribed to the Google Groups > "CakePHP" group. > To post to this group, send email to cake-php@googlegroups.com > To unsubscribe from this group, send email to > cake-php+unsubscr...@googlegroups.com For more options, visit this group > athttp://groups.google.com/group/cake-php?hl=en Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Re: Front-end for end-users and admins design
I am currently developing a large app which needed an area for the site owner to administrate the site, another area for organisations to administer their content and an area for standard site users to register and maintain their profiles. At first I thought it was sensible to do 3 apps on seperate sub- domains but you soon realise that you end up duplicating a lot of code and when you make a structural or cosmetic change it becomes a lot more work to replicate it across the 3 sites. Didn;t take me too long to integrate all 3 sites into the one app and it's so much better now. My vote, use routing or whatever other method you want but keep it all in the same app. HTH Paul. Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Re: Front-end for end-users and admins design
You may want to take a look at prefix routing (admin routing prior to 1.3) http://book.cakephp.org/view/950/Prefix-Routing. On May 18, 9:58 am, Andrei Mita wrote: > Thank Renato. Actually I was thinking to develop two separate cake apps: one > to run the website for the end-users and one, nested inside the main cake > app, to run the administration panel. > > for instance: mywebsite.com for end-users and mywebsite.com/oven for admins > > Any other suggestions? > > On Tue, May 18, 2010 at 4:27 PM, Renato de Freitas Freire < > > > > > > renat...@gmail.com> wrote: > > I like to do all the client system first, then I do another system, > > completly diferent to admin stuff. > > Even cake having the admin route, I dont like to use it. > > That way, I can put it in another url, so, guessing my admins urls is not a > > trivial thing... > > so, if one day, someone find a bug in cake admin route, my systems will be > > safe. > > > I just heard that there is some robots scanning cake's urls for an open > > scafold. So, I just want to prevent this things. > > I dont know if it is the better way, but the work is the same. > > > sry my bad english. > > > -- > > Renato de Freitas Freire > > ren...@morfer.org > > > On Tue, May 18, 2010 at 5:38 AM, Andrei Mita wrote: > > >> Hello, > > >> I'm getting ready to start a real project using Cake and the first > >> question is: how to separate controllers, actions and views for end-users > >> and admins. > > >> I mean, is there a recommended way of doing the splitting or is it enough > >> to create separate actions for end-users and for admins? > > >> For instance is it OK to have in Articles controller index() and > >> admin_index() ? > > >> Thanks > > >> Check out the new CakePHP Questions sitehttp://cakeqs.organd help > >> others with their CakePHP related questions. > > >> You received this message because you are subscribed to the Google Groups > >> "CakePHP" group. > >> To post to this group, send email to cake-php@googlegroups.com > >> To unsubscribe from this group, send email to > >> cake-php+unsubscr...@googlegroups.com >> om>For more options, visit this group at > >>http://groups.google.com/group/cake-php?hl=en > > > Check out the new CakePHP Questions sitehttp://cakeqs.organd help > > others with their CakePHP related questions. > > > You received this message because you are subscribed to the Google Groups > > "CakePHP" group. > > To post to this group, send email to cake-php@googlegroups.com > > To unsubscribe from this group, send email to > > cake-php+unsubscr...@googlegroups.com > om>For more options, visit this group at > >http://groups.google.com/group/cake-php?hl=en > > Check out the new CakePHP Questions sitehttp://cakeqs.organd help others with > their CakePHP related questions. > > You received this message because you are subscribed to the Google Groups > "CakePHP" group. > To post to this group, send email to cake-php@googlegroups.com > To unsubscribe from this group, send email to > cake-php+unsubscr...@googlegroups.com For more options, visit this group > athttp://groups.google.com/group/cake-php?hl=en Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Re: Front-end for end-users and admins design
Thank Renato. Actually I was thinking to develop two separate cake apps: one to run the website for the end-users and one, nested inside the main cake app, to run the administration panel. for instance: mywebsite.com for end-users and mywebsite.com/oven for admins Any other suggestions? On Tue, May 18, 2010 at 4:27 PM, Renato de Freitas Freire < renat...@gmail.com> wrote: > I like to do all the client system first, then I do another system, > completly diferent to admin stuff. > Even cake having the admin route, I dont like to use it. > That way, I can put it in another url, so, guessing my admins urls is not a > trivial thing... > so, if one day, someone find a bug in cake admin route, my systems will be > safe. > > I just heard that there is some robots scanning cake's urls for an open > scafold. So, I just want to prevent this things. > I dont know if it is the better way, but the work is the same. > > sry my bad english. > > -- > Renato de Freitas Freire > ren...@morfer.org > > > On Tue, May 18, 2010 at 5:38 AM, Andrei Mita wrote: > >> Hello, >> >> I'm getting ready to start a real project using Cake and the first >> question is: how to separate controllers, actions and views for end-users >> and admins. >> >> I mean, is there a recommended way of doing the splitting or is it enough >> to create separate actions for end-users and for admins? >> >> For instance is it OK to have in Articles controller index() and >> admin_index() ? >> >> Thanks >> >> Check out the new CakePHP Questions site http://cakeqs.org and help >> others with their CakePHP related questions. >> >> You received this message because you are subscribed to the Google Groups >> "CakePHP" group. >> To post to this group, send email to cake-php@googlegroups.com >> To unsubscribe from this group, send email to >> cake-php+unsubscr...@googlegroups.comFor >> more options, visit this group at >> http://groups.google.com/group/cake-php?hl=en >> > > Check out the new CakePHP Questions site http://cakeqs.org and help > others with their CakePHP related questions. > > You received this message because you are subscribed to the Google Groups > "CakePHP" group. > To post to this group, send email to cake-php@googlegroups.com > To unsubscribe from this group, send email to > cake-php+unsubscr...@googlegroups.comFor > more options, visit this group at > http://groups.google.com/group/cake-php?hl=en > Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Re: Front-end for end-users and admins design
I like to do all the client system first, then I do another system, completly diferent to admin stuff. Even cake having the admin route, I dont like to use it. That way, I can put it in another url, so, guessing my admins urls is not a trivial thing... so, if one day, someone find a bug in cake admin route, my systems will be safe. I just heard that there is some robots scanning cake's urls for an open scafold. So, I just want to prevent this things. I dont know if it is the better way, but the work is the same. sry my bad english. -- Renato de Freitas Freire ren...@morfer.org On Tue, May 18, 2010 at 5:38 AM, Andrei Mita wrote: > Hello, > > I'm getting ready to start a real project using Cake and the first question > is: how to separate controllers, actions and views for end-users and admins. > > I mean, is there a recommended way of doing the splitting or is it enough > to create separate actions for end-users and for admins? > > For instance is it OK to have in Articles controller index() and > admin_index() ? > > Thanks > > Check out the new CakePHP Questions site http://cakeqs.org and help others > with their CakePHP related questions. > > You received this message because you are subscribed to the Google Groups > "CakePHP" group. > To post to this group, send email to cake-php@googlegroups.com > To unsubscribe from this group, send email to > cake-php+unsubscr...@googlegroups.comFor > more options, visit this group at > http://groups.google.com/group/cake-php?hl=en > Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
Front-end for end-users and admins design
Hello, I'm getting ready to start a real project using Cake and the first question is: how to separate controllers, actions and views for end-users and admins. I mean, is there a recommended way of doing the splitting or is it enough to create separate actions for end-users and for admins? For instance is it OK to have in Articles controller index() and admin_index() ? Thanks Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
