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
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
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
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
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
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
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
