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
In an upcoming release we could add a migration with a sorting field. Maybe we could also use the alias to sort as they are not visible in the UI. So things like 0default 1abc would be possible? What do you think?
In an upcoming release we could add a migration with a sorting field. Maybe we could also use the alias to sort as they are not visible in the UI. So things like 0default 1abc would be possible? What do you think?
Using the alias may be a workaround (but we heavily use "fixed" container aliases).
A new sorting ID would be the preferred way and consistent to menu item's sort_index.
What steps will reproduce the problem?
Add multiple containers in the CMS.
What is the expected result?
Containers are sorted like in CMS Settings > Containers and thus by ID.
What do you get instead?
Containers are sorted by name in alphabetical order.
Additional infos
@nadar If you agree I can provide a PR.
The text was updated successfully, but these errors were encountered: