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

Moving nodes with Preset Nodetype filter #2800

Closed
markusguenther opened this issue Oct 19, 2020 · 1 comment · Fixed by #3822
Closed

Moving nodes with Preset Nodetype filter #2800

markusguenther opened this issue Oct 19, 2020 · 1 comment · Fixed by #3822
Assignees
Labels
7.3 8.3 Accessibility Bug Label to mark the change as bugfix UI & UX

Comments

@markusguenther
Copy link
Member

markusguenther commented Oct 19, 2020

Screen-Recording-2020-10-12-at-1

Steps to reproduce:

  1. Toggle the tree preset
  2. Move a Chapter node
  3. Refresh the tree

Observe the node disappear. It won't re-appear even after reload.
It's a backend issue, a bug in getNodeDataForParentAndNodeType as far as I can tell: it doesn't find nodes that have been moved but not yet published, but it's really hard for me to dig through that CR code... Maybe some backend people could lend a hand? @bwaidelich, could you?

Affected Versions

Neos: 4.x and up

UI: 4.x and up

Related: #1691

@markusguenther markusguenther added the Bug Label to mark the change as bugfix label Oct 19, 2020
@markusguenther
Copy link
Member Author

We had a great improvement with the PR #2794 for the handling with Nodetype presets but moving nodes still leads to issues. We will try to fix that now in a separate PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
7.3 8.3 Accessibility Bug Label to mark the change as bugfix UI & UX
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants