Manage translations from a single administrative interface with ease.
OverviewBack to top
The Translations Manager extension is an all-in-one tool to help simplify and improve the efficiency of translating Magento websites and modules to new languages, as well as editing existing translations.
The main ideas behind its construction are:
- To provide a single location in which translation data is reviewed and manipulated.
- To prevent duplications of translation definitions, that create scenarios where site administrators can't figure out why a string isn't being translated properly.
- To allow non-programmers the use of the powerful translation parameters through a simple UI.
- To allow site administrators to scan specific pages for translatable strings and then filter the translations list by page URLs.
- To replace the extensive parsing of CSV data with the more efficient use of database queries.
With these ideas in mind, we've created an administrative interface that allows site maintainers to control everything from a single location. Replacing Magento's mechanisms allowed us to add more functionality, and especially more control and ease-of-use for end users.
Following is the full list of features we've included:
- All CSV files are scanned once during the initial setup and then ignored by the system altogether. This removes the complications of searching for a text in multiple files until something works, as well as the encoding problems prevalent when saving CSV files for Magento. At any time when new CSV files are added or changed, they can be re-scanned with a click of a button. Re-scanning can be done for the whole locale folder or for specific files only.
- With the CSV files out of the way, defining module scopes doesn't require moving data from one file to another. A select box allows the user to choose which module scope this translation would apply to. This also means that selecting a scope isn't mandatory any more. If a translation is defined without a scope, it'll apply anywhere. If the same string is assigned a different translation for a specific scope, the default value will only be used where no specific values exist.
- Strings can now be set to a disabled state and re-enabled when needed, either in bulk or one by one.
- When editing strings, the translations can be set for each langauge by switching store view scopes. Everything is accomplished from the same page.
- Translation parameters are edited from a simple to use interface. You can add new parameters, remove existing ones, and set whether to use a dynamic value from Magento's code (as is by default) or replace those values with your own. Parameter values could be either static texts or Magento's custom variables. You can decide on the order assigned to parameters, whether they are your own or the ones hardcoded within the translation function.
- Inline translations work as before, only that the values are stored in the same place as all other translations and no duplicate entries are ever created. The results of working with inline translations can be reviewed and changed from the same administrative interface used for any other kind of translation. This is in comparison to the current state of affairs, in which one would only have access to inline translations from either the inline translation interface itself or from the raw database rows.
- The main administrative interface for managing translations allow sorting and filtering by: string, translated string, module scope, store views to which the string was already translated to, as well as the status (enabled or disabled).
- To find out which store views a string was already translated into and which ones it weren't, two methods are available. First, a column in the translations table displays the list of translated store views for each row. Second, the management area has a store scope filter that switches the translated string column to different languages, according to the store view that was chosen. This way, it's possible to easily overview the list and see where translations are missing.
- For every string, translations are per store view, and not per locale. This simplifies things and allows different translations for separate store views that use the same locale.
- A simple export button allows downloading the data in the table in either CSV or XML format. The CSV format contains all the data from the table, but could easily be transformed to Magento's translation CSV format if necessary.
- Bulk actions are available for deleting the strings, deleting just their translations in the current store view scope, and changing statuses (enabled/disabled).
- A 'Scan A Page' section is available, through which one can type in a URL path for a page in the store and that page will be scanned for translatable strings. On the management page, a filter by URL path option is available. Also, when editing specific strings, a table is available listing all the pages in which this string found when scanning. For *.phtml files, a file path and offset are also available if one wishes to find the actual file and modify it.
- Configuration options are available for not bypassing module/theme CSV file parsing. This is helpful for live websites that wouldn't want to take down the website until the all CSV data is migrated to the new extension, or for any other specific scenario that requires it. Any data defined within the extension's management area takes precedence over the CSV files.
Having said that, it's just as important to state what the Translations Manager extension is not. For instance, this extension is not meant to optimize processing times involved in Magento's translation process and does not come with any guarantee as to page load speed. Just as well, the Translations Manager doesn't replace any of the administration panel's translation features. Every place on the admin panel where one has the option of translating some value is a separate database table and each employs a slightly different mechanism, based on specific needs. In effect, the admin panel have no translation system of its own and thus an admin translation system as a whole ca not be replaced. And so, attribute labels are translated where configured, and so are attribute options. Product attribute values have a separate mechanism for translating values and are configured under the product edit form. Same holds for custom variables, shopping cart price rules, and every other part of the administration panel. Replacing all these sections with custom code would require replacing most of Magento's core and isn't a viable option.
Wheelbarrow's Translations Manager extension offers a management area for website translations. From there, you can view and filter within all the texts used in translation functions in your site. You can change the translated texts per store view, and review which strings were already translated to which language. The Translations Manager extension allows you to scan pages on your site so as to tell which strings appear on them, and you can filter based on paths to find what you need quickly. The extension enables the manipulation of translation parameters, as well as the utilization of Magento's custom variables within the translated strings.
The Translations Manager extension is licensed on a per domain name or IP address basis. Once your order is complete, you'll receive a license file by email that should be placed on your installation's folder before installing the extension. If you'd like to start out with a demo/local server or if you suspect you'll need to change the domain over time, we'll be happy to send you a modified license file with no attached fee. We do not offer an unlimited license change policy, simply to prevent exploitation by professional website builders and agencies.
Release NotesBack to top
- Compatible with CE: 1.7 1.8 1.8.1 1.9 1.9.1 1.9.2 1.9.3
- Stability: Stable Build
+ Performance optimization that reduces number of SQL queries per request
+ various bug fixes
+ Support for different translations for per area (admin/frontend)
+ Ability to filter by area
+ Support for different translations for different areas (frontend or admin)
+ Ajax-based page scanning for translatable strings
+ Stabler version that passed extensive unit-testing and GUI quality assurance phases.