Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
the most recent updated requires tinymce to be installed in 'sites/all/libararies/tinymce.' However, the Image_assist popup is still look in the old location. As a result, no images appear in the popup window: 'sites/all/modules/wysiwyg/tinymce/jscripts/tiny_mce/tiny_mce_popup.js?'
This does not appear to be an image assist issue as image assist without tinymce works just fine. Perhaps something didn't get updated?
Note, this was true in the dev version of May 16 as well as May 19
Comment | File | Size | Author |
---|---|---|---|
#4 | img_assist.wysiwyg-libraries.patch | 1.28 KB | sun |
#1 | img_assist-librarypath01.patch | 732 bytes | iva2k |
Comments
Comment #1
iva2k CreditAttribution: iva2k commentedI patched img_assist.module to use the right location when working with Wysiwyg TinyMCE.
@sun:
I'm not sure if I have to open a new issue in img_assist queue and post the patch there?
Comment #2
sunNope, we can simply move this issue. Good catch! :)
Only the patch is a bit dirty...
Comment #3
iva2k CreditAttribution: iva2k commented>Only the patch is a bit dirty...
Agree. It was indeed a quick hack to just patch 4 sites that I maintain. Given the state of flux for Wysiwyg API and no clear documentation, I guess only sun knows how to fix it so it won't break later.
Comment #4
sunThanks for reporting, reviewing, and testing! Committed attached patch to all 3.x branches.
A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.
Comment #5
tomsm CreditAttribution: tomsm commentedworks great!
Comment #6
ansorg CreditAttribution: ansorg commentedhello,
I run into the same issue using Image Assist 6.x-2.0-alpha3 and Wysiwyg 6.x-2.0
can this patch be applied there as well?
Comment #7
Frodo Looijaard CreditAttribution: Frodo Looijaard commentedI agree: the 2.0 branch has the same issue, and the same patch solves it.
Frodo
Comment #8
sunComment #9
sunCommitted to 2.x as well.