Problem/Motivation
When adding a new webform, the current interface language is used as original language.
If a content editor uses English as interface language, you always get an English translation of a webform, even if it is not needed in the system.
When you have language-specific content that is not translated to any other language, the webform should also only exist in the required language(s) not in the authors interface language.
At the moment, editors are forced to switch to a different interface language, to prepare a webform that uses the targeted language as original language, even if they can't read the button labels.
Steps to reproduce
Proposed resolution
Add a select box to choose the original language on webform add form, just like it exists for content translation. The interface language should be set as default value.
Remaining tasks
User interface changes
Additional select box to choose the original language on webform add form.
API changes
none
Data model changes
none
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | 3345252-9.patch | 2.23 KB | jrockowitz |
| #4 | interdiff.txt | 510 bytes | renatog |
| #4 | 3345252-4.patch | 1.01 KB | renatog |
| #2 | 3345252.patch | 884 bytes | mkalkbrenner |
Comments
Comment #2
mkalkbrennerComment #3
renatog commented#2 is good, but I'd suggest verify the options number and if there is only set we can set the select as "disabled" because don't make sense allow the user to select but we have only 1 option. So I think will improve the User Experience (UX)
Comment #4
renatog commentedSomething like this. What do you think?
Comment #5
jrockowitz commentedThe code from #4 is untested because it does not disable the ''langcode' dropdown. It feels like you are making code suggestions just to get a commit credit. Please slow down with your reviews and patches.
I think your suggestion is okay but we could only render the dropdown if it has more than 1 option.
Comment #6
mkalkbrenner@jrockowitz What about the patch in #2 in general? Do agree with my issue description?
We use the patch in production now and the editors are happy.
Comment #7
jrockowitz commentedThe patch from #2 makes sense. I need to download and test the patch locally. Maybe someone else can verify the patch.
Comment #8
jrockowitz commented@RenatoG I want to apologize for making this accusation. You have helped with a lot of tickets. It is important that every comment and patch it helps solve the task at hand.
Comment #9
jrockowitz commentedAttached patch incorporate the suggestion from #4 using #access and includes some test coverage.
Comment #13
jrockowitz commentedComment #15
renatog commented@jrockowitz you're wrong
Sorry but you can't ask that, it's a democracy
That’s ok