Navigating through the config translation listings for uploading individual config items is a pain. We need a way of managing them in bulks.
Create a bulk management form.
Code, review, test.
Added a form as in content bulk management for config.
Renamed "Manage" tab to "Content". Created "Config" tab.
Changed lingotek.config_translation service parameters for injecting the language-locale mapper.
Added requestTranslations(), checkTargetStatuses, deleteDocument and deleteMetadata to that service.
Added getConfigSourceStatus, getConfigTargetStatuses, requestConfigTranslations, checkConfigTargetStatuses, deleteConfigDocument, deleteConfigMetadata to that service.
Changed signature of updateConfig to receive a $mapper_id instead of a ConfigNamesMapper object.
The config metadata source status is saved keyed by language code, not by Lingotek locale. There is no update path needed as this was introduced in dev releases but not stable release.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 2637716-2.patch | 79.96 KB | penyaskito |
Comments
Comment #2
penyaskitoSee issue summary :)
Comment #4
penyaskitoComment #5
andypostThere's few
if (TRUEleftovers still needs to be fixedComment #6
penyaskito@andypost Thanks for reviewing! We probably are going to remove the checks for config objects, as they are mostly uploaded individually and make no sense requiring a profile when there is only one object of the same "type". That chunk remained there for reminding us to include it when we face config entities translation :)
Comment #7
andypostGood point, so better consistency with to do and issue