I want to show all language overrides in a list, like you can show al menuitems from all languages same with overrides from all languages and Admin and Site
Same like all menu items for example, it is easier to find everything when all is in list with search tools.
And to assign one override to more language. Because it can be that you translate the same.
Labels |
Added:
?
|
Category | ⇒ | com_languages Feature Request |
can maybe be feature request for next Joomla?
Does it really need a full refactoring?
From my "quick" look it just means that you move the "select language and site" for the new override to the override view instead of the overrides view
Labels |
Added:
?
|
Status | New | ⇒ | Discussion |
That was a "quick" look indeed.
The whole code is based on the userstate defined in the overrides view which is both used to filter the overrides manager and define the lang and client for a new override.
It would require preventing the language and client fields from being modified when the override already exist and is edited.
Also, It requires some Ajax magic to take into account a change of lang and client when editing an override as the search for a constant (or value) and client is done depending on the client.
It is possible indeed, but I call this a full refactoring because both models have to be heavily modified, their views, as well as filtering, the cache code, the js file, etc..
Everything you describe is how all components work so if this doesn't work that way it needs efactoring anyway.
The only thing unique about this component is the searching of keys/constants.
I will work on this at the weekend
...
Thank you @brianteeman
Labels |
Added:
J3 Issue
|
Status | Discussion | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-07-04 12:35:03 |
Closed_By | ⇒ | joomla-cms-bot |
Closed_Date | 2019-07-04 12:35:03 | ⇒ | 2019-07-04 12:35:04 |
Closed_By | joomla-cms-bot | ⇒ | alikon |
Set to "closed" on behalf of @alikon by The JTracker Application at issues.joomla.org/joomla-cms/22259
closing in favour of discussion going on at #24952 wich is 4.x based
This requires a full refactoring of the functionnality. Was already dicussed in a recent PR.