WYSIWYG / CKeditor / WYSIWYG image upload vs IMCE

Yes, Wysiwyg 6.x-2.x-dev (which will become the 2.1 release) supports CKEditor (including 'native' and 'Drupal' plugins to the same amount as FCKeditor does).
Have a look at #652410: Wysiwyg 2.1 for a rough estimate of what will happen before 2.1 is released.
I don't know when IMCE Wysiwyg Bridge or WYSIWYG ImageUpload module will get a new release, but it should not be too hard to get this working using their dev snapshots and a patch.

IMCE Wysiwyg Bridge uses editor-specific code ('native' plugins) to invoke the IMCE dialog and let it know where it should place the url to the selected image, thus each new editor supported by Wysiwyg module will require more code in IMCE WB. The latest incarnation of the code to do this for CKEditor is in #533168-34: Add support for CKeditor (comment 34). It may not be pretty to look at but works. Apply the patch to IMCE WB 6.x-1.x-dev and you should get the "browse" button in CKEditor's image dialog, just like in TinyMCE or FCKeditor. If not, I'm sure they'll appreciate the feedback in that issue.

I just talked to EugenMayer about wysiwyg_imageupload and he says he hasn't yet confirmed that his module works with CKEditor. But considering wysiwyg_imageupload is written to be editor-independent - it's a 'Drupal' plugin utilizing only Wysiwyg module's API to talk to editors - you should already be able to see the toolbar button and be able to use it. (If not, create an issue for wysiwyg_imageupload).

I hope that helped and not just added to the confusion. ;)

Hello,

well actually Twod is right concerning the wysiwyg_imageupload module. It is aimed to support every editor supported by the WYSIWYG module and it differs in how it does compared to the IMCE plugin. It only uses editor unspecific code + the WYSIWYG API bridge to actually "talk" to the editor you use right now.

As i can confirm the dialog worked with 2 / 2 editors i tried (tinymce/fckeditor) and the ckeditor should be close the fckeditor, i suggest that using the wysiwyg dev module with the current wysiwyg_imageupload module should work. If not, write me an issue. Iam not 100% sure but i think someone even tried it allready.

WYSIWYG image upload doesn't work with CKeditor for me. -- Or I just don't see an option to "Configure the WYSIWYG Module and edit your editors profile. Enable the "Image uploading" Plugin in the profile" in any of the CKeditor settings.

Maybe I'll try tinymce.

WYSIWYG image upload works pretty fine with CKeditor - iam using it.

I'm having issues with CKeditor and Image Upload as well. There's 2 problems.
1) Images get renamed to something like [[wysiwyg_imageupload:2:]] when previewed or saved, but show up fine in the editor.
2) Images can't be resized within the editor... Well, they can be, but saving doesn't save the resize.

Any ideas? Am I just missing a setting?

Thanks,
Jeff

So, I noticed that if I right click on the image in ckeditor and in advanced options remove all the class information, the images work fine.. Resizing, everything... Not exactly an easy work-flow though. What's the better fix for this?

jeffsawyer - Your issue is due to the fact that the wysiwyg_image_upload module installs a new "Input filter" which it requires in order to function. However, it does not enable it - this is your job.

1. Navigate to /admin/settings/filters and click "configure" for each format you use on your site.
2. On the following screen, enable "Drupal Wiki inline-images."
3. Clear all caches.

That will do it.

Thank you for all the support haikubear!

I have the same issue with the image uploads. Where do I find this exactly? in config - wysiwyg? - I have the ckeditor

@anne1960, it's hard to know exactly which issue you're having since this got transformed from a general support request "It doesn't work, what do I do?"-issue by the original poster to "Why do my images look like [[wysiwyg_imageupload:2:]]?" by a different user.

If you're having the second problem, see #9.
If it's something else then please create a new support request (this one is already "fixed/answered/solved") and include as much information you can about your site that may seem relevant. Error messages, additional plugins, theme-specific issues, installed Wysiwyg and editor versions, things like that.

Saved my bacon Haikubear....thanks

TNX haikubear