[#41109] - Unable to select frontend language for user
- Closed
- 1 Aug 2023
- Medium
- Build: 4.3.2
- # 41109
I have encountered an error that makes it impossible to assign frontend language to the user, neither in the frontend nor in the backend user profile settings.
screen shot 2023-07-03 at 18 21 49
Fix below...
backend:
/administrator/components/com_users/src/Model/UserModel.php (line 142)
$form->setFieldAttribute('language', 'type', 'frontend_language', 'params');
replace by
$form->setFieldAttribute('language', 'type', 'language', 'params');
frontend:
/components/com_users/src/Model/ProfileModel.php (line 152)
$form->setFieldAttribute('language', 'type', 'frontend_language', 'params');
replace by
$form->setFieldAttribute('language', 'type', 'language', 'params');
Why is that? Because I don't see any mention of "frontend_language" in the XML forms. I hope this fix will be included in j4.3.3
| Labels |
Removed:
?
|
||
joomla-cms-bot
- 
| Labels |
Added:
No Code Attached Yet
|
||
| Labels |
Added:
Information Required
|
||
ok, it's clear here. but what if third-party extensions are used, such as falang, where default home pages should be set to all? why is this necessary, why not leave standard language selection in user profile (frontend/backend)?
// Select the language home pages.
$query->select('l.home, l.language')
->innerJoin($db->quoteName('#__menu') . ' AS l ON l.language=a.lang_code AND l.home=1 AND l.published=1 AND l.language <> ' . $db->quote('*'))
->innerJoin($db->quoteName('#__extensions') . ' AS e ON e.element = a.lang_code')
->where('e.client_id = 0')
->where('e.enabled = 1')
->where('e.state = 0');
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/41109.
| Labels |
Removed:
Information Required
|
||
We had no issue for that until now. Could you check if this is caused by your template?
| Labels |
Added:
Information Required
|
||
This should be closed as not a bug in Joomla core
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2023-08-01 17:49:21 |
| Closed_By | ⇒ | chmst |
yes - after longer time and no additional information
I cannot replicate this issue. Have you activated content languages?
This is the FrontendLanguageFiled.