On the FCK web site Demo, the ENTER KEY is consistent between Firefox and IE.
It produces a new paragraph as expected.

However, in Drupal FCK it is not consistent, as follows:

Drupal 5.1
FCK Editor Module 5.x-1.x-dev (note: same result in 5.x-1.1)
FCK Editor 2.4.2

Before I go on, a note regarding versions:

On the Drupal FCKeditor main page, under "Compatability" it says "Please use the 2.3.2 release of FCKeditor for the moment - the module needs to be adapted for the 2.4 release."

But on the 5.x-1.x-dev Release Notes under "Small Bugs" it says "#114575 compatibility with the new 2.4 release of the fckeditor component" - it is NOT CLEAR if this REALLY MEANS "Small Bugs that have been fixed" and hence "compatability" or "Small Bugs that have not been fixed" and hence "incompatability" ... this is totally ambiguous ... but from the other two items under "Small Bugs" which are "#102141 msie 5.5 should be detected now" and "#115004 trying a quick and ugly fix for the popup function" I will LOGICALLY ASSUME that this REALLY MEANS "Small Bugs that have been fixed" and hence "#114575 compatibility with the new 2.4 release of the fckeditor component" rather than incompatibility.

However - in the "README.txt" within the module under "Requirements" - it says "FCKeditor 2.3.x (http://www.fckeditor.net/)" which implies that I CANNOT YET use version 2.4 of the editor

However - also in the "README.txt" - under "Installation" - it says "Download FCKeditor 2.x" which clearly implies that I CAN use version 2.4 of the editor, becuase version 2.4 is in the range described by 2.x

I am looking forward to crystal clear documentation, and even though I earn below the median wage I will be happy to pay a bounty when this is solved, becuase I think you are a GENIUS and deserve to be rewarded.

Now to my question:

WHAT SHOULD I DO to ensure that the ENTER KEY produces paragraphs in Firefox and IE, as per the FCK Demo site?

These are my current settings in "/fckeditor/fckeditor/fckconfig.js":

...
FCKConfig.DisableEnterKeyHandler = false ;
...
FCKConfig.EnterMode = 'p' ;
FCKConfig.ShiftEnterMode = 'br' ;
...

Are there other settings which are relevant to this issue? please help

Should these settings be moved to the other file "fckeditor/fckeditor.config.js" instead? I assume not?

Is this a known issue? Should I await a new release? Is there a quick and easy fix?

Thanks in advance, and sorry if I seem perplexed - but HONESTLY this is (now) the only thing standing between my clients and the internet (by the way my cleints are small academic departments at a university, on limited budgets, whom I choose to work for in preference to big commercial companies) and when I tell them "there are some minor cross-browser issues" well, naturally, they turn a kind of bluish purple colour.

Comments

ontwerpwerk’s picture

ontwerpwerk commented
Category: bug » support
Status: Active » Closed (works as designed)
  • the 5.x-1.1 version of the FCKeditor module works with FCKeditor 2.3.2 out of the box.
  • the universal keyboard is removed in FCKeditor 2.4.x, if you modify fckeditor.config.js you can use 2.4.x with the 5.x-1.1 module
  • the 5.x-1.x-dev version of the module will work with the 2.4.x version of FCKeditor.

The behaviour of the enter key in the editor is not dependent on the drupal module but of the FCKeditor component itself. I cannot fix that behaviour in the module, but you can modify the FCKeditor configuration.

The fckeditor.config.js file is the place to override any settings in the default configuration of the editor (That means you don't have to change anything in the default configuration file)