Scott Rutherford

So, not sure what algorithm Amazon are using to power their self optimizing links, but it doesn’t work – the books haven’t really changed in the 35 days its been on my blog. Of course I could be the exception but it seems to me to be, well, crap.

Quite disappointing really, I would of thought it would be possible to be a lot more targeted, especially as I already have links to their site from my posts so even returning the “others have bought” books would be an order of magnitude increase in performance.

I have been asked a few times for the code for the FCKeditor demo. So I thought I would put it up here for anyone to download, and by here I mean here.

The tar includes the fckeditor plugin, the ajax scaffold plugin and the bits to get them working together. You will need to create a db and update the config files though.

A few people have said they have been having problems with the text area not appearing in Firefox. This isn’t a problem I have had but for those of you who have, thanks to James Penny there is a solution…..

Simply add something like :width => ‘400’, :height => ‘200’ to the fckeditor_textarea call and you should get the editor appearing as expected. Obviously you can change the dimensions to suite your needs.

The solution also explains why I never saw the issue – I have always had the dimensions specified…...

I released a new version of the FCKeditor plugin today. It contains a couple of changes to the controller to fix a potential security issue and also a remote_form_for helper so that now you can do this:

<% fckeditor_remote_form_for :note,
                             :url => @options.merge(:controller => 'notes'),    
                             :editors => { :note => ['text'] } do |f| %>
  <%= fckeditor_textarea( "note", "text", :ajax => true )
<% end %>

You still need to use the original fckeditor_textarea call as as of yet there is no f.fckeditor_textarea method.

I am currently trying to add a check for IsDirty to prevent accidental unloading of the editor and also looking at using the FCKeditor_IsCompatibleBrowser() function to degrade gracefully.

N.B If you are upgrading you will need to delete the public/javascripts/fckeditor directory before reinstalling…