mirror of
https://github.com/silverstripe/silverstripe-translatable
synced 2024-10-22 11:05:59 +02:00
451576f36d
The redirect to pages overview was not working because the pages overview and page edit views share the same session namespace, and therefore the checks to see if we need to redirect to pages overview (i.e. if there is a translated record for the current page) matched also for the redirected request. Fixed by checking if we already are on the CMSPagesController before redirecting to it. |
||
---|---|---|
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.