Either go to Users -> User Notes -> New and select a User or go to Content -> Articles -> New, go to the Publishing tab and Created By, click on the modal button and then try to select a User for the field. There is the same problem when selecting a user in a custom component. When the modal window for selecting a user comes up a couple of errors occur and another error after clicking on the user to select it and nothing happens forcing to close the modal window not allowing to choose a user.
In the next figure you can see above the black line the two errors when the modal window pops up and below the line the error when clicking the user.
The next 3 screenshots's are to show the problem occurring while adding/editing an article, a user note and a record in an installed custom component.
Selecting the user successfully in the modal window returning to the edit view with user already selected.
Creates errors and doesn't allow choosing a user for the field in the add/edit view.
Joomla! 4.0.0-dev
OS: Linux Deepin 15.3
Kernel: 4.4.0-3-deepin-amd64
Google Chrome: 56.0.2924.76 (64 bit)
PHP: 7.0.12-2
MySQLi 5.7.15-1
Labels |
Added:
?
|
ok no worries, just wanted to double check
Status | New | ⇒ | Confirmed |
Category | ⇒ | com_users JavaScript |
@C-Lodder is this an issue for @dgt41?
Status | Confirmed | ⇒ | Information Required |
The multiselect.js is not compatible with the changes for no user!
I retested the issue both in firefox and chrome and it seems that the issue is gone entirely
So I guess this issue can be closed since the problem is solved :)
Joomla! 4.0.0-dev
OS: Linux Deepin 15.4
Kernel: 4.9.0-deepin12-amd64
Google Chrome: 60.0.3112.78 (64 bit)
Firefox: 57.0.1 (64 bit)
PHP: 7.0.20-2
MySQLi 5.6.30-1
Status | Information Required | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-12-12 06:46:15 |
Closed_By | ⇒ | franz-wohlkoenig |
Closed_By | franz-wohlkoenig | ⇒ | joomla-cms-bot |
Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/15325
closed as stated above.
Thanks for re-Test @rjcf18
No problem ;)
Could you try reverting back to jQuery 2.2.4 and see if this fixes the issue?