Problem/Motivation
The local translator has a checkout setting:
"Allow translations for enabled languages even if no user has the necessary abilities."
If this is allowed or not should be a global setting, not a translator checkout setting.
Currently one translator instance might have it enabled and the other not.
The submitting user should simply follow the global configuration.
Proposed resolution
Move the setting to the global settings page.
Remaining tasks
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | move_the_local-2668386-9.patch | 5.04 KB | thenchev |
| #9 | interdiff-2668386-9.txt | 886 bytes | thenchev |
| #7 | interdiff-2668386-7.txt | 2.26 KB | thenchev |
| #7 | move_the_local-2668386-7.patch | 5.37 KB | thenchev |
| #5 | move_the_local-2668386-5.patch | 4.89 KB | thenchev |
Comments
Comment #2
miro_dietikerStumbled upon this while review.
It has an additional setting now:
- Use admin theme in local translator
No idea how this could be asked per translator configuration.
Comment #3
miro_dietikerIt seems the admin theme setting is really saved per translator and additionally as a global setting.
So there's redundancy with this setting.
Comment #4
thenchev commentedStarting with this.
Comment #5
thenchev commentedInitial patch.
Comment #6
berdirDirection is fine, feedback on some smaller things below.
I'm surprised this works, I would have expected we still need an empty transalator definition?
You can use $this->config() in tests.
You don't have to call save() in the if anymore since we always do it below.
Comment #7
thenchev commentedAddressed #6
Comment #9
thenchev commentedTest fails without the "save". I think this should pass now.
Comment #11
berdirAh, the save is needed because the rebuild then accesses it again and needs the value to be saved. I guess we could refactor it to not save but not really worth it.
Committed, thanks.