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

DocumentTree is not reloaded when discarding node move changes #3184

Closed
klfman opened this issue Apr 8, 2022 · 1 comment · Fixed by #3503
Closed

DocumentTree is not reloaded when discarding node move changes #3184

klfman opened this issue Apr 8, 2022 · 1 comment · Fixed by #3503
Assignees
Labels
7.3 8.3 Accessibility Bug Label to mark the change as bugfix UI & UX

Comments

@klfman
Copy link
Contributor

klfman commented Apr 8, 2022

Description

After moving some documents in the document tree to a different parent, the document tree is not updated visually after a discard all.
Note: It works after a page reload, so the bug is only a neos-ui refresh problem, internally the move seems to have been reverted correctly.

This does not occur when moving a document within its parent.

doctree.mp4

Steps to Reproduce

  1. Create a nested document structure
  2. Move some documents from one to another parent
  3. Click "discard all"
  4. The document tree does not update to reflect the state before the changes (e.g. what the discard all reverts to)

Affected Versions

I saw this bug from Neos 7.1 through 7.3
Latest reproduced version is Neos 7.3.3, Flow 7.3.3 (the version running in the video above)

@mhsdesign
Copy link
Member

Before merging Wilhelms bugfix into 8.3, we should check what the behaviour is on 9.0 to avoid a regression after having it fixed.

grebaldi added a commit to grebaldi/PackageFactory.Guevara that referenced this issue Feb 15, 2024
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