Closed (fixed)
Project:
Entity connect
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Jul 2013 at 19:15 UTC
Updated:
1 Dec 2015 at 09:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
bryancasler commentedAlso experiencing this issue in the latest dev release.
Comment #2
Micha1111 commentedThis issue is 2 years old, but the problem still exists in rc4.
Marking this as a bug, because the funcionality is broken.
What happens with the data in entityreference field of the parent node ? Nothing is selected, if you open the parent form again !
BTW, it is very dangerous to allow users to delete such referenced nodes, because they can already be selected in other parent nodes. This ends up in unexpected data loss.
Comment #3
jygastaud commentedDeleting content is a core function and it is not the responsability of Entity Connect to deal with deleted nodes.
Entity Reference should.
I agree that it would be good to still come back to the form but it's not that simple as it can look.
Maybe we can remove the delete button when when the forms is load via entity connect button.
We need to check pro and cons of altering "normal" functionnality.
Comment #4
manojapare commentedPlease find patch file for the issue. In this patch, I have carried over the build cache id to node delete confirm form and thus entityconnect module can redirect back to parent form using the same.
Comment #6
manojapare commentedI have corrected the patch path and attached it.
Comment #7
rakesh.gectcrThe patch looks good. Passing the $cid, is great work. I am moving this to RTBC
Comment #10
jygastaud commentedThanks @manojapare for the patch.
I just push it in 7.x-1.x and 7.x-2.x branch.