In language overrides you have to first select context and language to find what you look for, it would be great if this section could work like all other components.
more consistent workflow in backend
cc @infograf768
Labels |
Added:
?
|
If I have understood this correctly the reason for having to select the language/client first is because the "new" button needs to know the language and client and without filtering the overrides it doesnt know.
For me this can be resolved in the same way that creating a new article is resolved.
In the edit form you add the ability to select the language/client
So the very first field on the edit form is the select language/client which can be prefilled if the list had been filtered
Am I missing something here. At least in theory this is a simple change
The best would be if it would be exactly the same usage as articles, I agree. Also a language override to be assigned to Al languages like articles and the identification which language overrides are missing.
the identification which language overrides are missing
Do you mean where a translator has not translated all the strings?
If so then I'm not sure how realistic that will be (at least for core) as the english string will often be in the language file so we cant tell if its not actually translated
I mean when I override "read more" to say "find out more" then it would be good for me as administrator to translate all the "read more" but often I miss a real overview in the override component. Maybe it could be even done in the Multilanguage Association Component?
oh I didnt realise that's what you meant. Definitely not a fan of that idea but if it scratches your itch ...
I guess it depends if you create a lot overrides or not. I can tell you that if you use a lot, it's absolute chaos which overrides exist, which not and what's maybe missing. Got a project with more than 800 Overrides and 9 languages and still stumble over strings that have been forgotten by the coworkers.
Labels |
Added:
?
No Code Attached Yet
Removed: ? |
That I would not be in favor as overrides are totally unrelated to associations and even multilingual sites (let's never forget that a site may propose multiple languages to let UI be defined on a user base but not be a multilingual site per se).
Concerning the present UI, it was a B/C improvement I did for J3.
Modifying it needs a total refactoring. See discussion here #22107 and original issue stated there.
I welcome any proposal using AJAX.