[#26489] - [4.0] Mail configuration component
- Closed
- 20 Feb 2020
- Urgent
- Build: staging
- # 26489
Sorry but this language filter makes no sense to me at all.
If I see this
And then filter on EN and see this
it makes no sense to me as a user why there is no english records displayed
When I look in the database then I can see the reason (and it almost makes sense technically) but then the UI needs to be different.
In addition I would expect from the ui that even if I understood why there was no EN record (yet) then there would at least be an ALL record
In fact is it ever possible to have an ALL record?
Or does it mean that ALL will display all the records that exist that have a specified language ie EN and FR and ES
If it is the latter then that's not correct as it is completely different to the rest of Joomla where ALL in a language filter means a record that is for all languages.
Either way it is wrong here
joomla-cms-bot
- | Labels |
Added:
?
|
||
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-10-06 19:28:17 |
| Closed_By | ⇒ | brianteeman |
I don't build multilingual sites so I never spotted it.
I still don't know if it's a bug or by design.
Not having a consistent UI will always be a bad ux
| Status | Closed | ⇒ | New |
| Closed_Date | 2019-10-06 19:28:17 | ⇒ | |
| Closed_By | brianteeman | ⇒ |
I would keep it consistent with the rest of Joomla:
"All" filter selects only items with language = *
"No filter" shows every item, whichever language it has
wilsonge
- | Labels |
Added:
?
|
||
Proposal for the listview and how to make this better: (I'm only listing the things that would change)
- The language column only lists those languages, that you have a translation for this template. So if you have 5 content languages and created templates for 2 of them for a template ID, then that column for that row would contain just those 2 languages.
- Clicking on the title of a template opens a "dropdown" (styling to be decided) and that contains a list of "Create/Edit template for [language]", signifying if the language already have a template or not.
I think that should solve a lot of the confusion. Question: Do you think that would be good enough? It would be rather easy to implement this.
| Labels |
Added:
?
|
||
The PR linked here has been merged. Is this still an issue or can we close this, thus solving a beta blocker?
| Priority | Medium | ⇒ | Urgent |
| Labels |
Removed:
?
|
||
Increasing priority as per guidelines for beta-blockers.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/26489.
| Labels |
Added:
?
|
||
| Labels |
Removed:
?
|
||
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-02-20 20:57:44 |
| Closed_By | ⇒ | wilsonge |
| Labels |
Removed:
?
|
||
I'm open for better suggestions here. The goal was to not have a row in the table per language and lots of confusing entries in general.
It's a pity that this is brought up AFTER the original PR has been merged and not in the year before that, where that PR was waiting for reviews.