- Issue created by @Balu Ertl
- Status changed to Postponed: needs info
5 months ago 2:22pm 17 June 2024 - 🇺🇸United States smustgrave
If installed correctly this is what you should see
- Status changed to Closed: outdated
4 months ago 8:21pm 21 July 2024 - 🇺🇸United States smustgrave
Since there hasn't been a follow up going to close for now.
- Status changed to Active
4 months ago 8:52am 22 July 2024 - 🇭🇺Hungary Balu Ertl Budapest 🇪🇺
I admit I missed checking the JavaScript console when first encountered the issue and opened the ticket. Now rechecked again and experienced the same, so reopened this ticket and retitled to describe the situation in more detail.
Some “probably-irrelevant-but-who-knows-might-come-handy” backend information:
- Web server: nginx/1.26.1
- DB driver: 10.11.8-MariaDB-ubu2204-log
- PHP version: 8.3.8
- Memory limit: 1024M
- First commit to issue fork.
- 🇬🇧United Kingdom clivelinsell
`jQuery.sort` was removed in v4, and D11 is using that version. It just needs a slight tweak to sort an array instead.
This is the first time I've used the MR flow, so apologies if something's not right.
- Status changed to Needs review
4 months ago 10:32pm 25 July 2024 - Status changed to RTBC
4 months ago 10:33am 26 July 2024 - 🇭🇺Hungary Balu Ertl Budapest 🇪🇺
Hi @clivelinsell → , thanks for the prompt solution. Now tested, commit d82cea90 eliminates the error message in the console and makes the list appear again indeed:
Regarding the merge request-based workflow: no worries, only one suggestion I would give. Usually better to create a separate branch for your suggested solution (eg.
123456-resolution-approach-one). The Drupal․org GUI offers an input field pre-filled with a suggestion based on the ticket title. If it sounds weird as a branch name (sometimes it's not optimal) then you're able to rename it arbitrarily before creating the issue repo:
Leaving the issue repository's default branches intact has a key benefit. This way anyone else coming up with a different idea for solving the same issue, can still open another branch (eg.
123456-resolution-approach-two) freshly stemming out from the original default branch (and open a separate marge request, of course). Finally, the project maintainers can decide which MR they agree with and get merged at the end. - Status changed to Fixed
3 months ago 4:59pm 8 August 2024 - 🇩🇰Denmark Uv516 Denmark
Drupal 10.3.2:
I have the same errors: No modules is showing at all.
When I save Module filter settings (admin/config/user-interface/module-filter), the settings in the three fields disappear and I get the error shown in the attached image. Automatically closed - issue fixed for 2 weeks with no activity.