mirror of
https://github.com/silverstripe/silverstripe-translatable
synced 2024-10-22 09:05:59 +00:00
2da48dfd65
This breaks code that tries to get all instances of SiteConfig like: ``` Translatable::disable_locale_filter(); $all = SiteConfig::get(); Translatable::enable_locale_filter(); ``` What was happening was that our populateSiteConfigDefaults method was getting called before the actual data list the users uses above is created, so it was re-enabling the locale filter before the augmentDataQuery function was called on the data list created for the user. Thus, they'd get a locale-augmented query and only get the SiteConfig for the current locale, and not all as clearly intended.
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-widgets/ to contribute translations, rather than sending pull requests with YAML files.
See the "i18n" topic on doc.silverstripe.org for more details.