First off, thank you for this module, it's been a huge help linking information and images together on one of my sites.
I've experienced an issue with this module where I have an extended field for an image that uses the WYSIWYG module (6.x-2.1). This works well until I click on the Add another item button for this image field. When I do, all of the text in the WYSIWYG field for the previous image is removed.
I had experienced this issue in the past with WYSIWYG on an HTML field where I allowed multiple values to be added, however, at that time the WYSIWYG API CCK Integration module fixed those issues.
Does anyone have any idea of how to resolve this, or where I should start looking?
Thanks!
Comments
Comment #1
ayalon commentedI can confirm this, I have the same problem and I don't know a solution.
Comment #2
alan d. commentedCan you confirm that this happens only with the ImageField + IF Extended modules and not ImageField only. Difficult to set up a test environment while traveling - so this helps to confirm the correct queue for this.
What integration method are you using? Insert? Wysiwyg API CCK Integration?
Cross posting #564854: Wysiwyg TinyMCE "Add another item"
Comment #3
nisaak commentedThanks Alan
Currently I'm only experiencing this with IF Extended fields on image fields. I am currently using WYSIWYG and WYSIWYG API CCK Integration for this and it is working for anything else that's not an image field.
If there is any other information I can supply to help with this please let me know.
Comment #4
alan d. commentedDue to the other issue that was listed for FileField, I think it is an issue with WYSIWYG API CCK Integration. Moving to that queue.
The Insert module is actively maintained, but I'm not sure if this is an option for you.
Comment #5
nisaak commentedI had a chance to do a little bit more testing with this today.
I noticed when working with this, that it works just fine using TinyMCE and with FCKEditor, however, it does not work with CKEditor like I was originally trying. My first guess is that it is likely an issue of something needing to be added to the wysiwygcck.js file similar to what is around line 11.