Re: Admin as a plugin
You can use the admin section as a plugin, something like: https://github.com/Maldicore/Admin Regards -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- 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. Visit this group at http://groups.google.com/group/cake-php?hl=en.
Re: Admin Section as plugin
You can use the admin section as a plugin, something like: https://github.com/Maldicore/Admin Regards -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- 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. Visit this group at http://groups.google.com/group/cake-php?hl=en.
Re: Admin Section as plugin
I've wrote a very simple plugin @ http://jobber.my/imz On Jan 31, 9:04 am, cronet cro...@gmx.de wrote: Hello, i want to create a plugin, which covers a little admin section, e.g. Usermanagement,Basic Authentication and website Settings The idea is to have a admin section which is easy maintainable, but also extendable to fit the needs of different projects... Do I run into problems creating this as plugin? Could it be possible involve other plugins in my admin plugin? Can I use the plugin layout in other plugins? One point could be the navigation menu. But if I store the menu array in the session i could easily extend the menu in other plugins... An example: I have my admin plugin ready, with basic stuff. In one project i need a newsletter module/plugin, which should be triggered by the admin section... The specific newsletter models, controller and views are handled by the newsletter plugin, but uses the layout of the admin plugin... Now, if i do adjustments to the basic stuff in the admin plugin, I simply update the plugin and could be sure, that the newsletter plugin is working as usual! I could easily update the admin plugin in several projects, without touching other areas of the different projects! Sure, all other plugins need to folllow a kind of conventions the admin plugin dictates... But that shouldn't a problem at all... Is this a stupid idea? Anyone of you implented something similiar before? I would like to hear your opinions ! Regards, AxlF 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
Admin Section as plugin
Hello, i want to create a plugin, which covers a little admin section, e.g. Usermanagement,Basic Authentication and website Settings The idea is to have a admin section which is easy maintainable, but also extendable to fit the needs of different projects... Do I run into problems creating this as plugin? Could it be possible involve other plugins in my admin plugin? Can I use the plugin layout in other plugins? One point could be the navigation menu. But if I store the menu array in the session i could easily extend the menu in other plugins... An example: I have my admin plugin ready, with basic stuff. In one project i need a newsletter module/plugin, which should be triggered by the admin section... The specific newsletter models, controller and views are handled by the newsletter plugin, but uses the layout of the admin plugin... Now, if i do adjustments to the basic stuff in the admin plugin, I simply update the plugin and could be sure, that the newsletter plugin is working as usual! I could easily update the admin plugin in several projects, without touching other areas of the different projects! Sure, all other plugins need to folllow a kind of conventions the admin plugin dictates... But that shouldn't a problem at all... Is this a stupid idea? Anyone of you implented something similiar before? I would like to hear your opinions ! Regards, AxlF 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
Admin as a plugin
I was wondering what the cons were to making 'admin' an actual plugin. It seems to me that this might make the app much more organized since regular and admin_* functions aren't mixed in the same file. What are your thoughts? Is there more overhead doing it this way? --~--~-~--~~~---~--~~ 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: Admin as a plugin
It also depends on how many people are working on your application. If, say, you have an admin programmer who only works on the admin section of your app, and a public side programmer who sticks to the non-admin areas, the project would be rather difficult to manage if you were to go about the admin_* route. You would constantly have more than one person modifying a file at a time, which becomes a complete hassle when using svn or some other versioning system. So, as far as I know, your other options are to go with a plugin, or a completely separate app. I am not sure about the overhead with plugins, I am really new to Cake still, so I need to do some more research on that. I am about to jump into the same situation you are, and I would like to use plugins, it just seems more logical from first look. ...and there's my 2 cents. --~--~-~--~~~---~--~~ 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: Admin as a plugin
Thanks for your reply! I agree with everything that you say. To me, it's kinda non conventional to mix the admin_* methods within non .. mostly because you can't look at the controllers and discern which ones have those methods until you open up the file. This way through a plugin you know what each controllers specifically does. Also, with plugins having their own AppController, you can easily set menus, etc .. Also, this is a breeze for ACL because you can wildcard controllers with Admin*:* (using felix g's SimpleAcl) On May 18, 11:27 am, Greg [EMAIL PROTECTED] wrote: It also depends on how many people are working on your application. If, say, you have an admin programmer who only works on the admin section of your app, and a public side programmer who sticks to the non-admin areas, the project would be rather difficult to manage if you were to go about the admin_* route. You would constantly have more than one person modifying a file at a time, which becomes a complete hassle when using svn or some other versioning system. So, as far as I know, your other options are to go with a plugin, or a completely separate app. I am not sure about the overhead with plugins, I am really new to Cake still, so I need to do some more research on that. I am about to jump into the same situation you are, and I would like to use plugins, it just seems more logical from first look. ...and there's my 2 cents. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
