[ANN] radiant-fckeditor 0.5 WYSIWYG Editor released

Ruby Apps Radiant CMS
1

Folks,

The existing FCKEditor plugin was out of date, so I spent a bunch of
time creating a new FCKEditor plugin, with the goal of making a
full-featured WYSIWYG page part editor that can easily be used. . .or
not. It can be added/removed at will from page parts.

Please see the page below for requirements and installation
instructions.

It has working file upload integration, is pretty good about not messing
with your Radius tags and you can switch between it and other filters
via the default “Filter” select menu.

I have tested on Firefox 2.0, IE 7 and Safari 3.1. It could use some
more testing - of course - but it should work on every browser FCKEditor
does. It’s based on FCKEditor 2.5 and some of Scott Rutherford’s plugin
at:
http://blog.caronsoftware.com/2008/2/6/fckeditor-plugin-0-4-3-released

It requires Shards, and I’ve tested it on 0.6.6, 0.6.7 and “edge”
Radiant.

It is vulnerable to the “multiple partial injection in 0.6.7 dev mode”
bug, so if you see more than one FCKEditor in a page part, that’s the
problem. Run in production mode, or upgrade 0.6.7 to the latest Radiant
from github.

The future:

  • An admin tab that allows toolbar button customizations,
  • Integration with scripts_n_styles to auto-populate the CSS class
    drop-down,
  • Integration with the PageAttachments plugin,
  • Integration with the Link Browser API to allow for point-and-click
    in-page linking,
  • You tell me!

Thanks! For now, kudos, suggestions, and bug reports can go to dan at
endpoint dot com.

–DJCP

2

Daniel Collis-puro wrote:

Folks,

The existing FCKEditor plugin was out of date, so I spent a bunch of
time creating a new FCKEditor plugin,

Sigh. It’s late. And it’s an extension, not a plugin.

–DJCP

3

Josh S. wrote:

I had trouble running the rake radiant:extensions:fckeditor:update task.

It copied a bunch of files until this error:

No such file or directory - …/radiant/vendor/extensions/fckeditor/
public/javascripts/fckcustom.js

From the looks of it, the only thing in this fckeditor/public/
javascripts folder is another folder called fckeditor.

I’ve looked at the rake task, but it’s not immediately apparent to me
what should be done, anyone have any suggestions?

Regards,
Josh

Josh,

Sorry about that.

In the file:

vendor/extensions/fckeditor/lib/fckeditor_file_utils.rb

comment out lines 70 and 71, the “copy_configuration” lines.

Or just wait a couple minutes for me to get my fix on github and clone
it again.

Again, I apologize.

-DJCP

4

Thanks, I got it all setup. You mentioned in the README that you want
to provide an interface to change the default toolbar, if I wanted to
do it manually for now where would I do it?

I think I just need to do: FCKConfig.toolbarSetName = “Basic”; in
fckconfig.js.

Is that correct?

5

This has been fixed, details at:

You should be able to “git pull” from the fckeditor extension directory
and run the “rake radiant:extensions:fckeditor:update” task again.

Thanks for hanging in there.

–DJCP

6

I had trouble running the rake radiant:extensions:fckeditor:update task.

It copied a bunch of files until this error:

No such file or directory - …/radiant/vendor/extensions/fckeditor/
public/javascripts/fckcustom.js

From the looks of it, the only thing in this fckeditor/public/
javascripts folder is another folder called fckeditor.

I’ve looked at the rake task, but it’s not immediately apparent to me
what should be done, anyone have any suggestions?

Regards,
Josh

7

Josh S. wrote:

Thanks, I got it all setup. You mentioned in the README that you want
to provide an interface to change the default toolbar, if I wanted to
do it manually for now where would I do it?

I think I just need to do: FCKConfig.toolbarSetName = “Basic”; in
fckconfig.js.

Is that correct?

Nope, you’d edit the config.js.erb view at:

$FCKEDITOR_EXTENSION_ROOT/app/views/fckeditor/config.js.erb

and make your changes there. The FCKEditor config file is emitted from
that view.

–DJCP

8

Josh S. wrote:

Sorry to keep going this thread going, but I’ve changed that file, but
it stills appears to be pulling the Default toolbar set. Do I need to
regenerate the configs with rake task? In fact, I’m not even seeing
the “simple” toolbar you have setup, although I do have a link for
config?class_name=Page.

Josh

No, that’s OK. I appreciate it, as it helps me to know what areas are
rough or might be good places to expand.

The “Simple” toolbar in config.js.erb is only in there as an example,
the editor is using the default toolbar.

And (I had to refresh my memory here) the way it works is you define the
toolbars in the config and then associate them with an FCKEditor
instance when the object is created in Javascript. Currently I don’t
specify a toolbar for the editor, so it’s picking up the default one.

You can just change the name of the toolbar in the view to:
FCKConfig.ToolbarSets[“Default”]
and customize it then. It will take effect, I just tested it.

All this config tomfoolery will go away when I build the admin tab.

Any other thoughts?

–DJCP

9

Sorry to keep going this thread going, but I’ve changed that file, but
it stills appears to be pulling the Default toolbar set. Do I need to
regenerate the configs with rake task? In fact, I’m not even seeing
the “simple” toolbar you have setup, although I do have a link for
config?class_name=Page.

Josh