On Tue, 19 May 2009, Joshua wrote: > I recently took over a symfony project that had already been built. I > can't make sense of the setup they are using here. How do I get > symfony to recognize the simple "reports" module? > > There is a backend application with module "reports" with no > designation in the schema. This module includes nothing but the > default setup after running this command. > > php symfony generate:module backend reports > > For better or worse it appears the backend application is using the > routing.yml to direct each module being used. "reports" module is > absent from routing.yml and no matter how I try to include it I get an > "oops" page and these errors in the logs. > > [19-May-2009 14:21:33] Action "reports/index" does not exist. > [19-May-2009 14:21:34] Action "sf/sf_default" does not exist. > [19-May-2009 14:21:34] Action "sf/sf_default" does not exist. > [19-May-2009 14:21:34] Action "sf/sf_default" does not exist.
By default, the index.php will be pointing to the frontend app. If the backend app is called 'backend' then there should be a backend.php file, so /backend.php/reports ought to get you to the reports module in the backend app. Note: routing is set on a per-app basis, so you should check apps/backend/config/routing.yml for backend app routes. -- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
