Using JMSi18nRoutingBundle : conflict about fosjsroutingbundle HOT 6 CLOSED

I'm not sure it's related to the JsRoutingBundle, and I don't want to add tweaks/hacks for other bundles that are not more than widely used.

from fosjsroutingbundle.

Of course I understand, but by default, the router uses the following to determine which locale to use for route generation:
1 . the _locale parameter which was passed to the generate() method
2 . use the _locale parameter which is present in the request context
3 . use the configured default locale

But with the JS generate() function all of that seems to be ignored. I don't understand why ...

from fosjsroutingbundle.

@z3yo The I18nRoutingBundle extends the Symfony router to choose the route name according to the locale (prepending it). The JS code is not changed when including the bundle. So you would need to use the route name generated with the locale in it.

from fosjsroutingbundle.

I replaced JMSi18nRoutingBundle by BeSimpleI18nRoutingBundle, it process with a different way and works well with FOSJsRoutingBundle.

from fosjsroutingbundle.

I was having the same issue as @z3yo because I was loading the router files in the "assetic" way in my base template:

{% javascripts output='js/routing.js'
  'bundles/fosjsrouting/js/router.js'
  'js/fos_js_routes.js' %}
  <script src="{{ asset_url }}"></script>
{% endjavascripts %}

This was not working for me even after dumping the routes with the fos:js-routing:dump command, since all i18n routes were prefixed with "LOCALE__RG__". and using Routing.generate('my_route') inside my javascripts wasn't findindg the appropriate route.

But then I thougt I could give a try at loading the fos_js_router resources the "traditional" way:

<script src="{{ asset('bundles/fosjsrouting/js/router.js') }}"></script>
<script src="{{ path('fos_js_routing_js', {"callback": "fos.Router.setData"}) }}"></script>

and it's working like a charm now. I don't even need to dump the js routes anymore as the fos.Router.setData method takes care of looking for exposed routes as far as I understand. Now I can successfully use Routing.generate('my_route') inside any js script and it just creates the route in the currently selected locale.

Hope it helps.

from fosjsroutingbundle.

fos.Router.setData is just the JSONP callback. Taking care of exposed routes is done server-side (and the different between the controller and the command looks weird)

from fosjsroutingbundle.