Closed (fixed)
Project:
Wysiwyg Fields
Version:
7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Jan 2012 at 12:40 UTC
Updated:
6 Feb 2012 at 03:00 UTC
I added a new field with type image, and made it a wysiwyg field so I got an image button for the wysiwyg.
Then added two images and saved the node, everything ok.
Then edit the node, doubleclick one of the images to make it active, hit delete - that image disappears, other one remains.
Then I submit the change and boom, both of the images are gone.
This also happens if I turn off JS and manually remove the other image from the image field and then remove the corresponding [wysiwyg_field] tag. Upon save both images are removed from the field.
Comments
Comment #1
chester_martin commentedI have this problem aswell. I'm not sure but if I uncheck "delete field items not inserted on Node save" from the advanced settings fieldset it seems to work.
Can you try unchecking that? maybe we can narrow the problem down a little.
Comment #2
decipheredI'm suspecting that the deletion of the one image is actually a misleading symptom of the true issue, but I would like to be proven wrong if possible.
What I suspect is happening is this:
1. You've created a node/entity with at least two images.
2. You've gone to edit said node/entity and have not invoked the Wysiwyg Field plugin (clicked the button) at all while editing the node/entity.
3. You've removed one of the images from the Wysiwyg and then saved the node/entity.
The problem appears to be that if you don't invoke the Wysiwyg Field plugin then the field widget is outside of the Form object and therefor not being submitted and being removed.
This is still quite a bit of a problem and definitely needs fixing. Can you confirm that this is the issue?
chester_martin,
Currently that checkbox does absolutely nothing, it needs to be re-implemented at some stage, and may need to be re-implemented sooner than later due to what it's supposed to do, but should not currently be having any effect on anything.
Comment #3
decipheredThe issue I outlined, that I believe this issue is also, has been fixed and committed to 7.x-1.x, a dev will be out within the next 12 hours.
Cheers,
Deciphered.
Comment #4.0
(not verified) commentededit, I think the other tag remains intact when the other is removed, but both of the files are removed.