You can obtain free community support for example through stackoverflow, or also through the Symfony2 mailing list.
If you think you found a bug, please create a ticket in the bug tracker.
If you take code quality seriously, try out the new continuous inspection service.
scrutinizer-ci.com
The bundle supports three different strategies out-of-the-box to make the most common scenarios a bit easier. You can switch between these strategies at any time.
jms_i18n_routing:
default_locale: en
locales: [en, de]
strategy: prefix
<jms-i18n-routing
default-locale="en"
locales="en, de"
strategy="prefix" />
Resulting URLs:
- /de/kontakt
- /en/contact
jms_i18n_routing:
default_locale: en
locales: [de, en]
strategy: prefix_except_default
<jms-i18n-routing
default-locale="en"
locales="de, en"
strategy="prefix_except_default" />
Resulting URLs:
- /de/kontakt
- /contact
jms_i18n_routing:
default_locale: en
locales: [en, de]
strategy: custom
hosts:
en: foo.com
de: foo.de
redirect_to_host: true
<jms-i18n-routing
default-locale="en"
locales="en, de"
strategy="custom"
redirect-to-host="true">
<host locale="en">foo.com</host>
<host locale="de">foo.de</host>
</jms-i18n-routing>
Whenever a pattern is matched to a different host?s locale a redirect is used,
unless redirect_to_host
is set to false, in which case a ResourceNotFoundException
is thrown which typically results in a 404 error.
Resulting URLs:
- http://foo.de/kontakt
- http://foo.com/contact
jms_i18n_routing:
default_locale: en
locales: [en, de]
strategy: custom
<jms-i18n-routing
default-locale="en"
locales="en, de"
strategy="custom" />
Resulting URLs:
- /kontakt
- /contact