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

[4.0] When moving child menus back and forth they don't sit well the second time #25270

Closed
uglyeoin opened this issue Jun 19, 2019 · 5 comments
Closed

Comments

@uglyeoin
Copy link
Contributor

uglyeoin commented Jun 19, 2019

Steps to reproduce the issue

Install J4
Install patch #25205
Ensure you have two menus
Create a parent item in both
Create a child item on the first parent, then create a second child item on the first child
Move the first child item to the second parent item in the other menu
It should move and bring its own child with it

Move the first child item back to the first menu parent
Both items move, but they don't appear to be part of the parent but sit in limbo on the parent item root although indented, orphaned

Expected result

Child moves to parent bringing all children (grandchildren?) with it

Actual result

Items on the second move become menu item root with no parent but appear to have a parent as they are indented

System information (as much as possible)

J4 Alpha 10

Additional comments

@ghost ghost added the J4 Issue label Jun 19, 2019
@ghost ghost changed the title When moving child menus back and forth they don't sit well the second time [4.0] When moving child menus back and forth they don't sit well the second time Jun 19, 2019
@brianteeman
Copy link
Contributor

From what I can tell the problem is that when you change the menu in the select then the menu items in that select dont update at the same time

@uglyeoin
Copy link
Contributor Author

Possibly you have described the problem better than I. Thank you.

@brianteeman
Copy link
Contributor

@uglyeoin dam - I remembered it but didnt find it when I created an issue the other day #36893

Happy to close mine but as its newer perhaps it will get noticed and acted upon in which case can you close this one.

@Quy
Copy link
Contributor

Quy commented Feb 2, 2022

Closing as duplicate. Thanks.

@Quy Quy closed this as completed Feb 2, 2022
@uglyeoin
Copy link
Contributor Author

uglyeoin commented Feb 3, 2022

Thanks both. It makes no odds to me whether this is the one closed or the other one, hopefully it gets solved :)

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

No branches or pull requests

4 participants