Describe the bug
This is a ux bug with heavy usability consequences for multingual platforms. It has been reproduced on Nightly.
As an admin adding content in a secondary language, I get errors preventing to save my changes, but no feedback of where to fix what error.
The source is that I didn't add the translations into the primary language. In previous versions of Decidim this was made explicit because the missing language was showing in red. In current versions however, languages are collapsed into a dropdown and the error is only visible once you open the dropdown and scroll into the content until you notice it. In other words, you have to guess where the error is.
To Reproduce
As an admin editing a multilingual platform's content, i.e. given a primary language set to english and secondary to french:
- I navigate the Admin in french,
- create a new component,
- and upon save get an error, with no indication of what to correct in order to properly save my component.
- If by chance I select a language dropdown next to a required field, I can see the primary language locales is missing and that this is the source of the error.
Test it by yourself here: https://nightly.decidim.org/admin/participatory_processes/hereslug/components/33/manage/proposals?locale=fr
Expected behavior
Expected: language dropdowns next to required fields should appear in error states (red)
Nice-to: Error message in banner should give useful context such as: please check required fields were translated to english
Screenshots
Stacktrace
No response
Extra data
- Device: MacBook Pro 13-inch, M1, 2020
- Device OS: Sequoia 15.7.2 (24G325)
- Browser: Firefox 145.0.2 (aarch64)
- Decidim Version:
- Decidim installation: https://nightly.decidim.org/
Additional context
No response
Describe the bug
This is a ux bug with heavy usability consequences for multingual platforms. It has been reproduced on Nightly.
As an admin adding content in a secondary language, I get errors preventing to save my changes, but no feedback of where to fix what error.
The source is that I didn't add the translations into the primary language. In previous versions of Decidim this was made explicit because the missing language was showing in red. In current versions however, languages are collapsed into a dropdown and the error is only visible once you open the dropdown and scroll into the content until you notice it. In other words, you have to guess where the error is.
To Reproduce
As an admin editing a multilingual platform's content, i.e. given a primary language set to english and secondary to french:
Test it by yourself here: https://nightly.decidim.org/admin/participatory_processes/hereslug/components/33/manage/proposals?locale=fr
Expected behavior
Expected: language dropdowns next to required fields should appear in error states (red)
Nice-to: Error message in banner should give useful context such as: please check required fields were translated to english
Screenshots
Stacktrace
No response
Extra data
Additional context
No response