On And Off The Rails

This release fixes the plugin for Rails 1.1.6. The fix is has been applied by overriding the new version of “safe_load_paths” in “routing.rb”.

However, I am not really happy with the current fix as it won’t play well with other plugins doing the same or with Engines. I think the answer is to convert this to a Rails Engine and let that system handle the routing.

It seems to me that the new fixes leave only two options to plugins developers:

1. copy any files to the apps directory when installing
2. use Engines

Not too sure I like copying loads of files around, if only because I don’t like the idea of the same thing existing in mulitple places within a single app. So that means Engines – therefore seems like a version of this functionality should be in the Core (especially if you are gonna stop the existing ways of dynamically creating a controller).

This fixes a couple of bugs and upgrades to version 2.3.1 of FCKeditor. The are a couple of changes to the way things work:

1) No controller, helper or view copied to the Rails app directory (you need to delete these if upgrading)

2) The editor files can now be included using

<%= javascript_include_tag :fckeditor %>

No spell check yet, and there are some issues with the file upload refreshing the resource browser after completion. Also there are no progress indicators for the ajax requests which can leave you wondering what (if anything) is going on.

Continue reading »

I have set up a project for the FCKeditor plugin on RubyForge. Now, you can just install it using:

ruby script/plugin install svn://rubyforge.org//var/svn/fckeditorp/trunk/fckeditor

This will take care of the install process meaning you can just include the editor in your views using the helpers described in my previous post.

These helpers also now include :height and :width options to set the size of the editor. Both of these options are used like so – :height => ‘400’.

Continue reading »