I have identified the responsible of this behaviour: the no_script_name option (in settings.yml).
When no_script_name is set to false all routes work correctly, but when it is set to true they don't work. My question is... why my frontend app works well with no_script_name set to true, but the backend does not? On 23 nov, 18:31, HiDDeN <davidmoralesmoj...@gmail.com> wrote: > I have a strange problem. In my development machine I have no problems > running all my application, but in production the backend doesn't work > well on the production environment. > > When in development environment, there's no problem. But when I switch > to prod environment, routes seem not to work. Every link I click makes > nothing, it reloads the same initial page. Other links return a 404 > page directly. > > I activated logs, and nothing is being written, so it seems that > Symfony is not catching any strange behaviour. It makes very difficult > to debug... > > Why is working in development and not in production? -- 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
