You are browsing documentation for version 5.0 of OroCommerce, OroCRM, and OroPlatform, maintained until August 2024 and supported until March 2026. Read version 5.1 (the latest LTS version) of the Oro documentation to get up-to-date information.
See our Release Process documentation for more information on the currently supported and upcoming releases.
Debug translator enables you to check and debug translations in the UI. To enable it, set option debug_translator to true in the config.yml file:
oro_translation: debug_translator: true
Additionally, refresh the backend and browser cache. All translated strings will then be wrapped into brackets, and untranslated strings will be wrapped into exclamation marks with dashes. Frontend translations have suffix “JS” to distinguish them from backend translations.
[Contact] - translated backend string !!!---Account---!!! - not translated backend string [Reset]JS - translated frontend string !!!---Refresh---!!!JS - not translated frontend string
Debug JS Translations¶
Debugging JS translations allows to turn off on fly JS translations generation, it can slightly boost performance on slow hardware configurations and make the application more stable on Windows. If kernel.debug is set to false, the value of debugging JS translations is ignored. To turn off JS translations generation, set option js_translation.debug to false in the config.yml file:
oro_translation: js_translation: debug: false
php bin/console oro:translation:dump
--locale option can be used to dump translations only for the specified locales:
php bin/console oro:translation:dump --locale=<locale1> --locale=<locale2> --locale=<localeN>