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

M2M previous sort order on items removed when ''select'' button is used to add existant item #8801

Closed
3 tasks done
chernandezweb opened this issue Oct 14, 2021 · 4 comments
Closed
3 tasks done

Comments

@chernandezweb
Copy link

Preflight Checklist

Describe the Bug

Hi, I'm having an issue with sorting m2m items. When I click ''select'' to add an existant item it refresh the list but all the sort number on the items are removed, so when I save the collection, it just throws away all the previous order.

To Reproduce

To reproduce it, you need have a list of items in a collection as m2m interface with the sort field attributed.

You just need to have already some items in the list then add an existant item with the ''select'' button.

What version of Directus are you using?

96

What version of Node.js are you using?

12.22.3

What database are you using?

MySql

What browser are you using?

chrome

What operating system are you using?

windows

How are you deploying Directus?

locally

@Oreilles
Copy link
Contributor

Cannot reproduce.
Please confirm that the problem is still present on latest release, and provide a better explanation and instruction for your issue.

@chernandezweb
Copy link
Author

Hi @Oreilles Yes I just test on newest release rc 99 and the issue is stil there. Here is a recording to show you what is happening

2021-10-22.09-53-26.mp4

.

@chernandezweb
Copy link
Author

When I create new it everything is fine. It just happens when I use ''Add Existing''.
Also this is a blank new directus project to test, so there is no other special configuration. It's just the simple use of a list of M2M items.

@rijkvanzanten
Copy link
Member

Duplicate of #8409

@rijkvanzanten rijkvanzanten marked this as a duplicate of #8409 Oct 26, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants