Duplicating base code is not ideal. It would be better on the long run to
have 2 differents applications, you are not forced to have a dedicaded
subdomain. You can initialize the Frontend and Backend from within a single
index.php by matching url.
On Thu, Jun 2, 2011 at 1:45 PM, keymaster
You can initialize the Frontend and Backend from within a single index.php
by matching url.
Thanks for the response, Thomas.
While in principle I understand what you are recommending, I have no clue on
what changes to make to get that setup.
Would you know of any example code somewhere on
On Fri, Jun 3, 2011 at 11:31 AM, keymaster ad...@optionosophy.com wrote:
You can initialize the Frontend and Backend from within a single
index.php by matching url.
Thanks for the response, Thomas.
While in principle I understand what you are recommending, I have no clue
on what changes
Just confirming to see if I understand correctly:
Two app folders - frontApp, backApp.
Single code base.
Single db.
Each userland bundle has AdminFront and AdminBack classes as well
as AdminFrontController and AdminBackController classes.
The AdminBundle config is
2 app folders with 1 different configuration for routing and templating.
You can share the Admin class, but this is not a good idea, it would be
better to have 2 dedicated Admin class, behaviors can change a lot between
super admin and simple user.
On Fri, Jun 3, 2011 at 2:12 PM, keymaster
I am not sure you can easily do that for now. The only good option will be
to create another dedicated application (FrontendKernel and BackendKernel).
With this solution you can customize all your previous points
On Wed, Jun 1, 2011 at 5:45 PM, keymaster ad...@optionosophy.com wrote:
Our site
what if we extended the CRUDController, overwrote the crud actions with
something like:
function edit(){
IF (current route is not 'admin/') THEN
//setup things for front end.
set new layout template
set new edit template
set new edit form
maybe... different namespaces...?
Sonata/AdminBundleFrontEnd
Sonata/AdminBundleBackEnd
Code is same in each.
In our config/config.yml, we map a different AdminClass and Entity for each
of the two AdminBundles to use.
We override the templates for AdminBundleFrontEnd as needed.
Feasable?
--
Our site uses the Sonata AdminBundle for our backend.
Now we would like to be able to also use it on our front end, so users can
manage their own properties (list, edit, delete, search/filter, etc.).
However, the following would have to be different for the front and back
end:
1.
have you gotten any response yet?
have you checked whiteoctober?
I have seen someone did this with basic custom CRUD stuff and it
simplifies all the magic and it is clear
ready made bundles scare me a bit since they have magic
keep me posted on your experience with whiteoctober
i believe that
10 matches
Mail list logo
