Problem/Motivation
Currently, the module's blocks can be created without the "locale" and "content_translation" modules activated. The interface translation block renders, but doesn't do anything when switching languages (since no interface translations are defined). The content translation block renders in a broken state: The block appears, but there is no dropdown menu to choose the languages from.
Let's discuss, if we should at least make the "locale" module mandatory. As when it is installed, the option to create a content translation block disappears, as expected.
REMINDER: Live prod config updates for all pre-running projects
DROPDOWN LANGUAGE STATS approx 7,500 →
sites with update running (known guest projects). major base concern is of course 4.x for this minor version move.
Steps to reproduce
- user can not translate content on node page without wider core setups (site not more 'translation ready')
Proposed resolution
- Make the locale & content_translation modules dependent. see problem.
Remaining tasks
- update module .info.yml
- update readme
- ?? hook_update related notices, install notice helpers?? (new config).
- update project page (@skaught)
User interface changes
- enables some wider drupal core modules required for content translation.
API changes
Data model changes
- wider core translation modules will be enabled.