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

BUG: Moved asset only appears in target collection after reload #204

Open
lorenzulrich opened this issue Oct 12, 2023 · 4 comments
Open
Assignees
Labels
Bug Something isn't working

Comments

@lorenzulrich
Copy link
Contributor

Description

If an asset is "moved" from one collection to another, it is not visible in the target collection without a reload of the module.

Steps to Reproduce

  1. Create at least two collections A (first level) and B (second level).
  2. Upload file to collection B.
  3. Click file in collection B and select collection A as "Collection".

Expected behavior

  • The file disappears from the view as I moved it to collection A.
  • When I open Collection A, I see the file.

Actual behavior

  • ✔️ The file disappears from the view as I moved it to collection A.
  • 🐛 When I open Collection A, I don't see the file. As soon as I refresh the page, it shows up.

This only happens when moving a file up in the hierarchy, in my case from collection B to A. Moving from A to B works flawlessly.

Affected Versions

Neos: 8.3
UI: 8.3.4
Media Module: 0.13

@lorenzulrich
Copy link
Contributor Author

It also seems that the state of the footer is not properly updated. It still shows "1 assets" and the pagination:

image

@lorenzulrich lorenzulrich changed the title Moved asset only appears in target collection after reload BUG: Moved asset only appears in target collection after reload Oct 12, 2023
@Sebobo
Copy link
Member

Sebobo commented Oct 13, 2023

In theory I have all necessary cache flushes in place. It might be the assets list of the parent is still cached and I need to flush it separately. Will need further investigation.

@Sebobo Sebobo self-assigned this Oct 13, 2023
@Sebobo Sebobo added the Bug Something isn't working label Oct 13, 2023
@Sebobo
Copy link
Member

Sebobo commented Jul 1, 2024

This bug is really a bit annoying as it doesn't happen every time. Some timing issue when the various instances and caches are being updated.

@Sebobo
Copy link
Member

Sebobo commented Jul 22, 2024

1.3.0 includes a partial fix. But there are still some cases in which it doesn't reliably work. Like a 50/50% chance when reassigning an asset.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
Status: In progress
Development

No branches or pull requests

2 participants