You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When moving a document or collection with children only the moved nodes path is updated and not the childrens. The sort_index of the new siblings of the moved node doesn't seem to get updated either. Are we missing something or is this a known bug?
The issue only persists within private workspaces. It corrects itself once I publish all my nodes, but I don't have a correct preview within my private workspace if I don't publish.
When manually indexing a moved node it seems like ElasticSearch sometimes takes the wrong version since Neos keeps a "movedto" node in the database until the changes are published.
The text was updated successfully, but these errors were encountered:
When moving a document or collection with children only the moved nodes path is updated and not the childrens. The sort_index of the new siblings of the moved node doesn't seem to get updated either. Are we missing something or is this a known bug?
The issue only persists within private workspaces. It corrects itself once I publish all my nodes, but I don't have a correct preview within my private workspace if I don't publish.
When manually indexing a moved node it seems like ElasticSearch sometimes takes the wrong version since Neos keeps a "movedto" node in the database until the changes are published.
The text was updated successfully, but these errors were encountered: