You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
install Joomla 4.0.0 beta 1 with no sample data
login to admin as super admin
attempt to create new module
Go to Menu Assignment tab
Select "only on the pages selected"
Note the yellow warning "No Matching Results"
Expected result
Actual result
unclear yellow warning "No Matching Results" - not sure WHAT results it was looking for as all I have done is open this panel so far.
The warning should be hidden by default.
Additional comments
It looks related to the sieve filter search - because if you search for crap you are left with the yellow warning, and if you then search for Home (a valid menu item name) the yellow warning is not there.
The text was updated successfully, but these errors were encountered:
PR for joomla#29489
### Steps to reproduce the issue
create new module
Go to Menu Assignment tab
Select "only on the pages selected"
Note the warning "No Matching Results" at the bottom of the page
### After PR Test 1
As above No warning message
### After PR Test 2
In the search box enter something that will not match a menu
Warning message correctly displayed
### Note
a js rewrite of treeselect **might** be another solution
Steps to reproduce the issue
install Joomla 4.0.0 beta 1 with no sample data
login to admin as super admin
attempt to create new module
Go to Menu Assignment tab
Select "only on the pages selected"
Note the yellow warning "No Matching Results"
Expected result
Actual result
unclear yellow warning "No Matching Results" - not sure WHAT results it was looking for as all I have done is open this panel so far.
The warning should be hidden by default.
Additional comments
It looks related to the sieve filter search - because if you search for crap you are left with the yellow warning, and if you then search for Home (a valid menu item name) the yellow warning is not there.
The text was updated successfully, but these errors were encountered: