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

Perspectives: Objects of wrong class can get added to wrong path via Copy/Paste or Cut/Paste #865

Open
BlackbitDevs opened this issue Mar 12, 2025 · 0 comments

Comments

@BlackbitDevs
Copy link
Contributor

BlackbitDevs commented Mar 12, 2025

Steps to reproduce:

  1. Open "PIM" perspective on https://demo.pimcore.com/admin/?perspective=PIM
    It contains a custom view for Car objects on the left side and one for Category objects on the right side
    Image
  2. Right-click category /products in the Categories custom view -> Cut
  3. Right-click /aston martin on the Cars custom view and select "Paste > Paste cut-out element"

After pasting, the object is not visible in /aston martin in the Cars custom view. And it stays visible in the Categories custom view because this tree does not get refreshed.
After reloading Pimcore it is even worse: The object completely disappeared as it is not visible in the Cars custom view (because this custom view only shows objects of class Car) nor in the Categories custom view (because the object is in a different path now).

But when you switch to Default perspective, you will see that the object indeed got copied to /aston martin (or better /Product Data/Cars/aston martin):
Image

We need to prevent pasting elements to custom views which do not allow the class name of the copied element.

@BlackbitDevs BlackbitDevs changed the title Perspectives: Objects of wrong class can get added to wrong path via Copy/Paste Perspectives: Objects of wrong class can get added to wrong path via Copy/Paste or Cut/Paste Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant