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 fields
}
parent::edit();
}
Also:
Define additional front end routes to that controller, and repoint the
existing backend routes to this new controller.
Override and extend the constructor in the Admin class to set different
form/list/filter properties depending on the route?
Might that be feasable?
The other options: writing a new search/filter/pagination bundle, or making
a separate admin app on a subdomain are not ideal solutions.
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
