Problem/Motivation
The locale deploy allows a site to manage all of its translation deployments via it's own project repository and prevent the translation system from getting translations from localize.drupal.org outside of its own Drush commands. One of the things it does is remove the version information from translation files. This results a warning in _install_prepare_import() due to assumptions that code makes.
Steps to reproduce
- Install minimal
- Enable locale_deploy module
- Add a language
- Run drush locale-deploy:localize-translations
- Import the site from configuration drush si --existing-config
Proposed resolution
There's nothing for this code to do in this situation.
Remaining tasks
User interface changes
None
API changes
None
Data model changes
None
Release notes snippet
N/a
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | 3406697-nr-bot.txt | 90 bytes | needs-review-queue-bot |
Issue fork drupal-3406697
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3406697-fix-notice-in
changes, plain diff MR !5714
Comments
Comment #2
alexpottThis is very related to #3182660: [PP-1] Make translation filename pattern configurable during install
Comment #4
alexpottComment #5
chr.fritschLooks good :)
Comment #6
quietone commentedI'm triaging RTBC issues. I read the IS, the comments and the MR. I didn't find any unanswered questions.
I left suggestions in the MR for coding standards. Plus I think a comment is needed so I had a go at that, perhaps someone has a better one.
Comment #7
alexpottI addressed @quietone's review. As the changes were minimal, setting back to rtbc.
Comment #8
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #9
alexpottFixed merge conflict.
Comment #10
quietone commentedAssigning to myself to commit tomorrow
Comment #13
quietone commentedCommitted 220f04c and pushed to 11.x and 011f36a and pushed to 10.2.x. Thanks!