mirror of
https://github.com/silverstripe/silverstripe-translatable
synced 2024-10-22 11:05:59 +02:00
1c40751d51
When editing a page in the default locale, a double ajax request was done for the editing page. This was caused by no locale-parameter being set in this case, which caused the default locale parameter to be added and a new ajax request was made due to this. The extra ajax request caused the loading-animation to appear after the edit page was loaded, which looks weird. Fixed by doing a redirect immediately the CMSPagesController is loaded and no locale is set, so that the default locale parameter gets set at this stage. |
||
---|---|---|
code | ||
css | ||
docs/en | ||
javascript | ||
lang | ||
tests/unit | ||
_config.php | ||
composer.json | ||
LICENSE | ||
README.md |
Translatable module for SilverStripe CMS
Introduction
Allows translation of DataObject and SiteTree records into multiple languages.
See /docs/en/index.md
for details.
Requirements
- SilverStripe 3.0 (both cms and sapphire modules)
Maintainers
- Ingo Schommer
Issues
TODO
This module was originally part of the SilverStripe CMS core codebase. While the bulk of the logic has been separated out into this module, there are still many places across SilverStripe CMS which this modules relies on:
- CMSBatchActionHandler->handleAction()
- ContentController->handleRequest()
- ContentController->ContentLocale()
- ErrorPage::response_for()
- LeftAndMain->init()
- ModelAsController->getNestedController()
- RootURLController::get_homepage_link()
- SearchForm
- SiteConfig
- SiteTree->RelativeLink()
- SiteTree->getSiteConfig()
These APIs mostly require either hooks for an Extension subclass, or refactoring to allow better customization.