[#47484] - [5.4] Fix dropdown filter URL sync in Administrator Menus (#47447)
- Closed
- 30 Mar 2026
- Medium
- Build: 5.4-dev
- # 47484
- Diff
- Francis1104Ol:fix-dropdown-url
User tests: Successful: Unsuccessful:
Pull Request resolves # .
Pull Request resolves #47445
- I read the Generative AI policy and my contribution is either not created with the help of AI or is compatible with the policy and GNU/GPL 2 or later.
Summary of Changes
Fixed the dropdown filter URL in the Menus administrator view.
- Updated
default.phpincom_menusto correctly preserve selected filter in URL.
Testing Instructions
- Go to Administrator → Menus → Main Menu.
- Use the dropdown filter to select a category.
- Verify that the URL updates correctly without breaking the filter
Actual result BEFORE applying this Pull Request
Dropdown filter selection did not update the URL.
- Page reload resets the selected filter.
Expected result AFTER applying this Pull Request
Dropdown filter selection did not update the URL.
- Page reload resets the selected filter.
Link to documentations
Please select:
-
Documentation link for guide.joomla.org:
-
[x ] No documentation changes for guide.joomla.org needed
-
Pull Request link for manual.joomla.org:
-
[x ] No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Administration com_menus Front End Plugins |
| Title |
|
||||||
This is obviously completely wrong (even when you ignore the unrelated files)
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-03-30 21:43:22 |
| Closed_By | ⇒ | muhme | |
| Labels |
Added:
PR-5.4-dev
AI Generated
|
||
@Francis1104Ol Thank you for your contribution!
In Joomla administrator lists (such as Menus, Articles, etc.), filter values are typically stored in the user session rather than in the URL. This behaviour is therefore expected and not considered as a bug to be fixed.
Therefore we will go ahead and close this issue.
For your next PR please test your changes locally before opening a PR. Additionally, please ensure that the PR description, test instructions, and source code changes are consistent with each other and the PR doesn't contain unrelated code changes.
And anyone submitting a PR must ensure that all CI checks have been passed before we can proceed.
@Francis1104Ol Unless you confirm that you have followed our guidelines on generative AI, we cannot accept this PR. And looking at the title: does this PR resolve #47445 rather than #47447? If so, please change it.