On Mon, 14 Jun 2010, Parijat Kalia wrote:
> *When you created the frontend application, the production front controller
> was named index.php. As you can only have one index.php file per directory,
> symfony creates an index.php file for the very first production front
> controller and names the others after the application name.*
Yes, its stated several times in the docs.
> Now when I look into routing.yml of my backend app, here is what it states:
>
> *homepage:
> url: /
> param: { module: default, action: index }
>
> default_index:
> url: /:module
> param: { action: index }
>
> default:
> url: /:module/:action/**
>
> So clearly, the instruction that it would default it to the name of the app,
> did not take place, it still shows index as the default parameter...
In the routing above, index is the name of an action, nothing to do with
the controller filename...
> changed wherever 'index' is to ''backend' to mimic the name of my app...but
> that did not help either...
Yes, because of what I said above.
Its clear, you dont understand about routing and controllers, so reading
up on it might be useful.
--
--
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
