Closed jamarisi closed 10 years ago
+1 I have same issue in symfony 2.4. Route in request is "ltRGuser_login_check", but it should be "user_login_check"
I'm also having this issue.
From what I can see Route:match($url)
is no longer used... Route::matchRequest(Request $request)
is used as of 2.4.
+1
Just a wild guess here: login and login_check shouldn't really be translated, max I'd pass maybe the locale as a get param to get a redirect to the original translation after logincheck Meaning one should prefix the route names with to stop them being translated?
Hello, yesterday I updated one of my projects to Symfony2.4 and I'm having problems with the i18n since then. First, my language switcher generates only routes for the current language. It ignores the _locale param and if I'm currently using the es locale, it generates all the links with the same locale.
It was working perfectly with Symfony2.3.
Second, I'm having problems with the security configuration. In my security.yml I have something like
But now the login_path, check_path and path in logout are no longer recognized. There are no exceptions when the file is parsed, but the listeners are not invoked when the form is submitted. It works when I add the localized paths, like esRGfos_user_security_login, but I cannot hard code the localized path for every locale. Like the first problem, it was working fine with Symfony2.3.
The bundle configuration is:
Any ideas that I can try to fix these issues?
Thank you in advance.