mirror of
https://github.com/silverstripe/silverstripe-translatable
synced 2024-10-22 09:05:59 +00:00
9e37602ef7
When you publish a node in the default locale it calls forceChange to make every field behave as if it has changed. The problem in Translatable is then it would think that you actually changed the class of the default locale node and it would force a change on every translation. This was unnecessary when you have not actually changed the class name. If you have a great deal of translations this was causing a significant lag when you publish anything in the default locale.
Translatable module for SilverStripe CMS
Introduction
Allows translation of DataObject and SiteTree records into multiple languages. Note: This module was originally part of the SilverStripe CMS 2.x codebase.
Usage
Requirements
- SilverStripe Framework 3.1+ and CMS 3.1+
- Note: For SilverStripe 2.3/2.4 support, please use the core built-in version (no module required)
Maintainers
- Ingo Schommer
Contributing
Translations
Translations of the natural language strings are managed through a third party translation interface, transifex.com. Newly added strings will be periodically uploaded there for translation, and any new translations will be merged back to the project source code.
Please use https://www.transifex.com/projects/p/silverstripe-translatable/ to contribute translations, rather than sending pull requests with YAML files.
See the "i18n" topic on doc.silverstripe.org for more details.