Closed (fixed)
Project:
WYSIWYG image upload - Inline images for your WYSIWYG
Version:
6.x-2.8
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Dec 2010 at 00:59 UTC
Updated:
15 Dec 2010 at 00:56 UTC
Comments
Comment #1
eugenmayer commentedWell that looks like a bug. Thanks for reporting.
Can you reproduce it every time or is that just a sideeffect?
Comment #2
traceelements commentedI can reproduce it every time. Also, thanks for the great module. I like it much better than Image Assist
Comment #3
eugenmayer commentedThanks for confirming, will fix this for 2.9
Comment #4
traceelements commentedThanks!
Comment #5
miro_dietikerreferring to a somehow similar case
#992438: node image changes if reused in comment
Comment #6
tseven commentedI am getting the same result of the source image displaying as "http://mysite.com/sites/default/files/imagecache//" but I haven't been able to isolate what is triggering it.
I have noticed that the node still holds the proper reference ie: [[wysiwyg_imageupload:137:]]
but there is no corresponding entry in the database.
After updating to the latest version WYSIWYG image upload (2.8) I've had 3 specific images disappear (seemingly randomly). Images created before the update are fine. Those three problematic images where created after the update and only belong to a single node which doesn't get touched. Seems like something else is deleting the entries.
Have some sort of garbage collection functions been implemented in this version? Something which might be mistaking valid images for old/deleted images?
Thanks
Comment #7
eugenmayer commented@6 Thanks for the investigation. Yes, there is such a method.
On cron run, after a treshhold of i think 30 minutes, every temporary entry gets removed. If you have a entry like [wui..:ID] in your content, but the corresponding relation is missing in the database, the garbage collection has removed it.
Did your images have been added to a CCK textfield-area? If yes, be aware that 2.8 does not support CCK at all, 2.9 will do so.
Comment #8
eugenmayer commentedthat one was related to #992438: node image changes if reused in comment as miro mentioned above and is a dublicate. Its fixed in 2.9 therefore