User tests: Successful: Unsuccessful:
Pull Request for Issue #33784.
The Multilingual Associations can only be used for multilingual website with Associations enabled in System - Language Filter plugin. This PRs modify code to only show Multilingual Associations menu item from Components menu backend if the conditions meet.
Multilingual Associations menu item always displayed.
Multilingual Associations menu item always displayed if conditions meet
| Status | New | ⇒ | Pending |
| Category | ⇒ | Modules Administration |
@sandramay0905 What options you are talking about? Could you show me a screenshot? Thanks
Patch OK.
We could leave the Options imho as anyway I guess we should not introduce disabling a specific extension/component in com_config depending on the language filter setting.
The Options page would load ok and when closed, will anyway show the alert.
The only remaining hint to inform admin users that the site can be multilingual with associations, if desired.
I have tested this item
| Status | Pending | ⇒ | Ready to Commit |
RTC
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2021-05-12 09:58:37 |
| Closed_By | ⇒ | richard67 | |
| Labels |
Added:
?
?
|
||
Thanks!
Maybe now we will be allowed to only show the multilingual sample data in the same situation?
@brianteeman I haven't tried that multilingual sample data, so I don't know. If the sample data install additional languages, enable the Language Filter plugin to make the site ready multilingual, then It should stay there. If not (just setup data like articles... only), then I think we can do the same check with how we are doing in this PR.
@joomdonation The multilingual sample data doesn't install languages. But it does all the rest, enable the Language Filter plugin, create menus and home menu items ...
I have tested this item✅ successfully on 9b63c5f
Off topic this pull request, but shouldn't in the options the multilingual associations also be hidden? If yes, i can make a issue.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/33815.