Remove dependancy on FCKeditor, support WYSIWYG

I would imagine a lot of people who are using FCKeditor will eventually end up switching to the WYSIWYG module. I personally need the extra settings that WYSIWYG module doesn't provide.
I use CKeditor which is the newer rebuilt version of fckeditor.

http://cksource.com/about

http://drupal.org/project/ckeditor

The module does sound useful but I'll have to wait until other editors are supported before I can try it out.

+1 FCKEditor is deprecated. WYSIWYG is the future.

+1 To clarify we would like to work towards supporting WYSIWIG module in general if this is possible. Not only CKEditor..!

Subscribe - for some sites, I use CKEditor (drupal module + editor) since it has a bit more advanced customization options.

But as time goes on, and WYSIWYG support for more advanced features (like custom toolbar settings) gets better, I will still use the CKEditor editor, but wrapped in WYSIWYG. So WYSIWYG module support would be a very good idea.

Definetly +1 on this. If this is fixed, the module would prove 10 times more useful to everyone.

+1 for WYSISYG API support.

Me too...

+1 Agreed.

+1 I am dying to use this module, but lack of WYSIWYG support could kill it for me.

Yes, WYSIWYG is must have. Very excited to try this.

Subscribing....

+1 for all the reasons listed above.

Another vote for WYSIWYG

+1 for single CKEditor module - much more to the point then WYSIWYG

+1 for single CKEditor module - seems as though if FCKeditor is supported that CKeditor might be relatively easy to add(?)

+1 - just came across this module and realized that we extended the nodepicker.module to do this. Would've been much better to use this module instead if it integrated with WYSIWYG api.

+1 WYSIWYG.

should have an update on this in the next couple of days.

Subscribing and anticipating the new version.

added ckeditor plugin support with 1.2, still no word on wysiwyg yet.

Node Reference / Embed Media Browser supports WYSIWYG, and uses the same filter as Node Embed, allowing for easy migration.

I've implemented the Wysiwyg api and have everything working. I couldn't create a diff because there are new folders and I don't have CVS access. I've attached a tar with the changed module instead.

jec006 thanks for this (and the CKEditor integration) if you apply for a CVS account I'll make you a co-maintainer.

http://drupal.org/cvs-application/requirements

FYI, I have made jec006 co-maintainer of this project.

Any update on getting this revised functionality committed to CVS?

@pwolanin: this got committed by jec006 back in September 8. I couldn't get it to work anyway.

I just figured out that the commit was incomplete. The tar.gz file in #22 includes a plugins directory that was never committed to the repository.

The attached file provides a patch that will add the text files of that tgz back, and includes a couple of simple fixes to some persistent warnings introduced by this module.

Note that the node_embed/plugins/images/icon.gif is NOT included in the patch and must be added to the repository before a commit.

I am marking this RTBF, as I have just tested it, and I haven't altered jec006's code. :)

Using this code with the latest releases of WYSIWYG w/CKEditor I get a Javascript error when clicking on the Node Embed button:

Uncaught TypeError: Cannot read property '$' of null /sites/all/modules/wysiwyg/editors/js/ckeditor-3.0.js?N:186
Drupal.wysiwyg.editor.instance.ckeditor.addPlugin.CKEDITOR.plugins.add.init.pluginCommand.exec /sites/all/modules/wysiwyg/editors/js/ckeditor-3.0.js?N:186
... (see attached image for full error)

The patch in #27 worked for me.

Hey Guys,

Sorry for the delay - i'm gonna try to fix the check in and make a new release.

I didn't do the original check in of the code and it looks like the new folders contents weren't added (as you said).

I've created a new release (6-x--1-4) to resolve this issue. Marking as fixed.