This release tidies up some of the things I thought I’d got right with the last one, doh. However, it turns out I had overlooked the paths for the spell check and the resource manager. Both of these now dynamically configure so that you can place your install anywhere you fancy. Unfortunately there is a single piece of configuration now required, if, and only if your app is hosted away from the root of the server.
Oct 022006
Sep 272006
This release fixes an issue with the base path to the editor being hardcoded into the helper. The problem arose when hosting an app using named virtual hosts and aliases. e.g. hosting your app at www.mydomain.com/scotts/railsapp instead of www.mydomain.com/railsapp.
This should now all work……..
Sep 212006
There is a new version of the FCKeditor plugin up. This fixes a problem I found when running tests. The alias method in the init.rb file was being called for every test and causing an infinite recursion. The README has also been fixed to remove the various typos people have found (thanks for the feedback).
As before you can get the plugin using:
ruby script/plugin install svn://rubyforge.org/var/svn/fckeditorp/trunk/fckeditor
There is also a demo
Sep 112006
This release is basically a bug fix. The only really change is to apply the patch kindly provided by Nicola Piccinini which sorts out an issue with file upload from inside the resource manager.
There are a couple of other changes to do with the install and version numbers, but that is all internal to the plugin.
Sep 082006
There is a new version of the FCKeditor Rails plugin available details of how to get it and a demo are here.
This version fixes a problem with having multiple editors open at once on the same page and also adds a helper to allow multiple editors on the same Ajax form. This also now works with static html forms but you can just use the standard form helpers for that.
Aug 262006
I’ve just released the next version of the FCKeditor plugin. The main change in this version is the addition of the spell check functionality using ASpell. A big thank you to Ken Pratt for providing the patch for that and at the same time providing a solution (I hope) to the routing issues that some people have had.
If you already have this plugin installed you can upgrade by just deleting the existing install and getting it again. If you have altered the fckcustom.js file then you will need to add:
FCKConfig.SpellChecker = 'SpellerPages';
to it . If not just delete that too before reinstalling. You also need to be sure that ASpell is installed along with any dictionaries you want to use (If you are on windows check the README for the expected install directory).
Aug 172006
Ok, I admit I overreacted slightly to the Rails bug and have now realised I was talking rubbish. So here is a release that works with 1.1.6 and plays well with everybody. It also updates the install code and moves the fckcustom.js config file out of the base fckeditor install directory. This means that you can update or delete the install without having to worry about removing any customizations you have made.
In the new fckcustom.js (public/javascripts/fckcustom.js) there is also now an example of creating your own toolbar which can now be included using
<%= fckeditor_textarea("object", "field", :ajax => true, :toolbarSet => 'Simple', :width => '400', :height => '200') %>
As Jeff Owens has pointed out there are still issues with the Flash upload and I will try to address those as soon as possible.
Aug 152006
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:
- copy any files to the apps directory when installing
- 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).
Aug 132006
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.
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’.
