Includes advanced Image/Media, File and Link handling, plugin support, and an Administration interface for editor configuration.
You may have seen the dire warnings about the WYSIWYG editor messing up your custom HTML code in an article. Not with JCE: if it's good HTML, JCE leaves it alone. That feature alone makes this editor a winner for me.
JCE is a dream come true. It worked beautifully first time! I almost can't believe the ease and extent of customisation offered by this lovely little tool.
Makes me wonder why I didn't search for a new editor earlier! (Maybe I have just come to accept that many things in Joomla need a little hack to get them working as I want! ;-)
@tgelvin - Removal of the iframe-tag is a security feature of Joomla 1.5.8 and has nothing to do with JCE!
Note also that you have to activate html-upload in the configuration of JCE in order to get the uploads work with 1.5.8-defaults!
Well you're in luck because I have just released an IFrame plugin for JCE 1.5.x - http://www.joomlacontenteditor.net/downloads/plugins/jce15x.html
I haven't tried yet to write a plugin for JCE (this editor has a well thought architecture), but I think that this should be feasible.
One suggestion: to make a plugin to include community builder profile elements, or at least pictures of users. This could be added in the link plugin.
We chose this over our second favorite editor FCK because, of two reasons:
-You can stretch the side of the editor.
-Professional Look. JCE is the nicest looking editor around.
The only problem I have encountered is when running the editor in Firefox with Adblock or Adblock Plus.
Some of you probably don't even know about the Advanced Link Editor because Adblock is blocking the icon, advlink.gif, that must be clicked to activate the tool.
To allow the icon to be shown you need to go to Tools->Addons->Adblock (or Adblock Plus), click on the "Options" button, and then the "Add Filter..." button at the bottom left. Type in @@advlink and hit the "Ok" button.
An admin on the JCE forums (quickly) indicated that this issue would be resolved in a future release.