The error message that displays when you try to configure FCK editor but you haven't put the actual editor there (just the module) is as follows:

The FCKeditor component is not installed correctly. Please go to the FCKeditor homepage to download the latest version. After that you must extract the files to sites/all/modules/fckeditor/fckeditor/fckeditor/ and make sure that the directory sites/all/modules/fckeditor/fckeditor/editor and the file sites/all/modules/fckeditor/fckeditor/fckeditor.js exist. Refer to the readme.txt for more information.

The destination to extract the files to is incorrect - it currently reads sites/all/modules/fckeditor/fckeditor/fckeditor/ whereas there should be one less "/fckeditor" - it should be sites/all/modules/fckeditor/fckeditor/ - I believe this is extremely important since many users will run into this problem.

Comments

wwalc’s picture

wwalc commented

Interesting... this is what I've got:

The FCKeditor component is not installed correctly. Please go to the FCKeditor homepage to download the latest version. After that you must extract the files to /drupal61/sites/all/modules/fckeditor/fckeditor/ and make sure that the directory /drupal61/sites/all/modules/fckeditor/fckeditor/editor and the file /drupal61/sites/all/modules/fckeditor/fckeditor/fckeditor.js exist. Refer to the readme.txt for more information.

and I even cannot understand how could you get this warning message in 6.x-1.3-rc7 (explanation below).
All three paths are created with this code:

    '%modulepath' => base_path() . $module_drupal_path .'/fckeditor/',
    '%modulesubdir' => base_path() . $module_drupal_path .'/fckeditor/editor',
    '%modulefile' => base_path() . $module_drupal_path .'/fckeditor/fckeditor.js

so if $module_drupal_path was set to 'sites/all/modules/fckeditor/' I do not understand where did that three /fckeditor/ parts took from(?).

Please let me know if you are still able to reproduce it and where is the fckeditor.module file located.

wwalc’s picture

wwalc commented
Status: Active » Fixed

Found it in 6.x-2.0, it was in the 6.x-2.x version actually, am I right?

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.