If there is e.g. paragraphs with file upload field in a node, and you clone the node the reference is targeting to the same (paragraph) entity. If you edit one of these page and update file field in file paragraph and user will download/access this file. But if user try to download/access file in other cloned pages it will show "You are not authorised to access this page"
To reproduce this issue :
1. Create paragraph with file upload(e.g. File paragraph) field and add this reference to your content type
2. Create node with "File Paragraph" and upload file under it.
3. Clone your node it will create new page, under new cloned page update file field and upload new file under it and save.
4. In Cloned page if you try to download/access uploaded file it will download.
5. Check original node and try to download/access uploaded file under it, it will show you "You are not authorised to access this page"
Comments
Comment #2
nitinsp commentedComment #3
hawkeye.twolfNote that the current behaviour, which leverages Node::createDuplicate(), creates new revisions of the existing paragraphs item, rather than creating entirely new paragraph entities on the cloned node. I'm not sure Node Clone even wants to get in the business of supporting contrib-specific entities, but at the very least there should be a giant warning on the project page and README saying,
And if we do want to support Paragraphs, we could make it a sub-module.
Consider combining this issue with either of:
Comment #4
nitinsp commentedHi derek.deraps,
Thanks for your use full reply, Is any alternate solution for node clone? If u have any idea please share.
Or Can we create node clone pragmatically with new target_id?