Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Widget types in "Add Widget" dropdown on layers page aren't displayed in any useful order #17424

Closed
rwawr opened this issue Jan 29, 2025 · 1 comment · Fixed by #17426
Closed

Comments

@rwawr
Copy link
Contributor

rwawr commented Jan 29, 2025

Describe the bug

On the Edit Widgets and Layers page under Design > Widgets in the admin panel, when clicking the "Add Widget" button in any zone, the list of widgets is displayed in whatever order happens to be returned from the call to ContenteDefinitionManager.ListTypeDefinitionsAsync, whereas the list is ordered alphabetically by DisplayName when adding a widget to a flow part (code in FlowPart.Edit.cshtml). It would be much easier to find a desired widget type if the list were ordered alphabetically on the Edit Widgets and Layers page as well. I imagine that would just be a one-line change in OrchardCore.Layers.Views.Admin.Index.cshtml, which I'm happy to submit a PR for.

Orchard Core version

To Reproduce

  • Go to the Edit Widgets and Layers page under Design > Widgets in the admin panel
  • Click the Add Widget button
  • Observe that widgets are not ordered by display name

Image

Expected behavior

Widgets should be ordered by display name

Copy link
Contributor

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants