You are here

README.txt in FCKeditor - WYSIWYG HTML editor 5.2

Same filename and directory in other branches
  1. 5 README.txt
  2. 6.2 README.txt
  3. 6 README.txt
CONTENTS OF THIS FILE
---------------------

 * Overview
 * Required components
 * More information and licence
 * Requirements
 * Configuration
 * Installation troubleshooting
 * Plugins: Teaser break and Pagebreak
 * Uploading images and files
 * How to enable the built-in file browser
 * Modules: Image Assist
 * Modules: Link to content (EXPERIMENTAL)
 * Link to content + Path Filter (EXPERIMENTAL)
 * Upgrading instructions
 * Help & Contribution
 * Credits 
 
Overview
--------
This module allows Drupal to replace textarea fields with the
FCKeditor.
This HTML text editor brings many of the powerful functions of known
desktop editors like Word to the web. It's relatively lightweight and
doesn't require any kind of installation on the client computer.

Required components
-------------------
To use FCKeditor in Drupal, you will need to download the FCKeditor
http://www.fckeditor.net/

More information and licence
----------------------------
FCKeditor - The text editor for internet
Copyright (C) 2003-2006 Frederico Caldeira Knabben

Licensed under the terms of the GNU Lesser General Public License:
    http://www.opensource.org/licenses/lgpl-license.php

For further information visit:
    http://www.fckeditor.net/
    http://drupal.fckeditor.net

Requirements
------------
  - Drupal 5.x
  - PHP 4.3.0 or greater
  - FCKeditor 2.3.x or greater (http://www.fckeditor.net/)

Configuration
-------------------
   1. Enable the module as usual from Drupal's admin pages.
   2. Grant permissions for use of FCKeditor in Administer > User Management > Access Control
   3. Under Administer > Settings > FCKeditor, create the fckeditor profiles. 
      In each profile you can choose which textareas will be replaced by FCKeditor, 
      select default toolbar and configure some more advanced settings
   4. For the Rich Text Editing to work you also need to configure your filters for the users that may access Rich Text Editing. 
      Either grant those users Full HTML access or use the following:
      <a> <p> <span> <div> <h1> <h2> <h3> <h4> <h5> <h6> <img> <map> <area> <hr> 
      <br> <br /> <ul> <ol> <li> <dl> <dt> <dd> <table> <tr> <td> <em> <b> <u> <i> <strong> 
      <font> <del> <ins> <sub> <sup> <quote> <blockquote> <pre> <address> <code> 
      <cite> <embed> <object> <param> <strike> <caption>.
   5. To have a better control over line breaks, you may disable Line break converter in the chosen filter (recommended).
   6. Modify the fckeditor.config.js file to custom your needs (optional).
      You may copy the needed configuration lines from the default FCKeditor configuration settings (modules/fckeditor/fckeditor/fckconfig.js), 
      the lines in fckeditor.config.js will override most settings.
      WARNING: clear browser's cache after you modify any of the javascript files.
      If you don't do this, you may notice that browser is ignoring all your changes.

Installation troubleshooting
----------------------------
If your FCKeditor does not show you must check if all files are extracted correctly. 
The directory /drupal5/modules/fckeditor/fckeditor/ should have the following files:
fckeditor.js, fckconfig.js, fckstyles.xml, fcktemplates.xml, fckeditor.php,
fckeditor_php4.php, fckeditor_php5.php and a directory named editor.
The correct directory structure is as follows:

    modules
       fckeditor
          fckeditor.module
          fckeditor
             _samples
             editor
             COPY_HERE.txt
             fckconfig.js
             ...

If you're still having problems, scroll down to the "Help & Contribution" section.
             
Plugins: Teaser break and Pagebreak
-----------------------------------
By default, FCKeditor module comes with two plugins that can handle teaser break (<!--break-->) and pagebreak (<!--pagebreak-->). 
You can enable any (or even both) of them.

   1. Open /drupal5/modules/fckeditor/fckeditor.config.js and uncomment these three lines:

            FCKConfig.PluginsPath = '../../plugins/' ;
            FCKConfig.Plugins.Add( 'drupalbreak' ) ;
            FCKConfig.Plugins.Add( 'drupalpagebreak' ) ;
            

   2. The second step is to add buttons to the toolbar (in the same file). 
      The button names are: DrupalBreak, DrupalPageBreak. 
      For example if you have a toolbar with an array of buttons defined as follows:

      ['Image','Flash','Table','Rule','SpecialChar']

      simply add those two buttons at the end of array:

      ['Image','Flash','Table','Rule','SpecialChar', 'DrupalBreak', 'DrupalPageBreak']

      (remember about single quotes).

Uploading images and files
--------------------------

There are three ways of uploading files: By using the built-in file browser, by using a module like IMCE or using the core upload module.

How to enable the built-in file browser
---------------------------------------
The editor gives the end user the flexibility to create a custom file browser that can be integrated on it. 
The included file browser allows users to view the content of a specific directory on 
the server and add new content to that directory (create folders and upload files).

   1. To enable file browsing you need to edit the connector configuration file in your fckeditor module directory, the file should be in:

          /drupal5/modules/fckeditor/fckeditor/editor/filemanager/connectors/php/config.php
          (FCKeditor 2.5+)

          or

          /drupal5/modules/fckeditor/fckeditor/editor/filemanager/browser/default/connectors/php/config.php
          and
          /drupal5/modules/fckeditor/fckeditor/editor/filemanager/upload/php/config.php
          (FCKeditor 2.3.x - 2.4.x)

      In this file(s) you will need to enable the file browser by adding one line that includes file with the special authentication function for Drupal (filemanager.config.php). Add this code:

          require_once "../../../../../filemanager.config.php";
          (FCKeditor 2.5+)

      or

          require_once "/absolute/path/to/drupal5/modules/fckeditor/filemanager.config.php"
          (FCKeditor 2.3.x - 2.4.x)

      straight below this line:

          $Config['UserFilesAbsolutePath'] = '' ;

      The config.php file also holds some other important settings, please take a look at it and adjust it to your needs (optional).
      
   2. As of Drupal 5.2, additional step is required: locate file named settings.php inside 
      your drupal directory (usually sites/default/settings.php) and set $cookie_domain variable to the appropriate domain (remember to uncomment that line). If you not do this, FCKeditor will claim that file browser is disabled
   3. Enabling file uploads is a security risk. That's why you have to grant a separate permission to enable the file browser to certain groups.
   4. Lastly, adjust the File browser settings for each profile.

Modules: Image Assist
---------------------
Image Assist can be integrated with FCKeditor.
To do this, simply copy the modules/fckeditor/img_assist_fckeditor.js file to modules/img_assist/img_assist_fckeditor.js.
Note: this version of the FCKeditor module only supports the 1.x versions of the Image Assist module.

Modules: Link to content (EXPERIMENTAL)
---------------------------------------
Link to content module can be integrated with FCKeditor.
ATTENTION: this module is not yet compatible with FCKeditor :(

The unofficial version of Link to content module compatible with FCKeditor can be downloaded here:
 * 5.x-1.7	(2007-Oct-04)
     http://drupal.fckeditor.net/download/linktocontent-fckeditor-5.x-1.7.tar.gz 
 * 5.x-2.x-dev	(2008-Mar-06)
     http://drupal.fckeditor.net/download/linktocontent-fckeditor-5.x-2.x-dev.tar.gz

Alternatively, you may apply required changes in the linktocontent code by yourself.
To do this, download the linktocontent module from http://drupal.org/project/linktocontent.
The minimal list of required changes in this module is available here:
  http://drupal.fckeditor.net/linktocontent.patch

Installation:
Follow the instruction from INSTALL.txt attached to the linktocontent module.
Then do the following steps to add Linktocontent button to the FCKeditor toolbar:

By default, FCKeditor module comes with two plugins that allows you to use linktocontent and linktonode features.
You can enable any (or even both) of them.

   1. Open /drupal/modules/fckeditor/fckeditor.config.js and uncomment these three lines:

            FCKConfig.PluginsPath = '../../plugins/' ;
            FCKConfig.Plugins.Add( 'linktonode', 'en,pl' ) ;
            FCKConfig.Plugins.Add( 'linktomenu', 'en,pl' ) ;

   2. The second step is to add buttons to the toolbar (in the same file).
      The button names are: LinkToNode, LinkToMenu. 
      For example if you have a toolbar with an array of buttons defined as follows:

      ['Link','Unlink','Anchor']

      simply add those two buttons at the end of array (or somewhere in the middle):

      ['Link','Unlink','LinkToNode','LinkToMenu','Anchor']

      (remember about single quotes).

Link to content + Path Filter (EXPERIMENTAL)
--------------------------------------------
Linktonode plugin (read above) is also compatible with Path Filter module.
You can create links to your sites using special syntax: internal:node/23.
Download and install Path Filter module: http://drupal.org/project/pathfilter
Edit your FCKeditor profile:
    1. Go to "Advanced options" section
    2. In "Path Filter & Link To Content integration" choose either
       "Link using internal: links" or "Allow user to select between paths and internal links"

Upgrading instructions
----------------------
This instruction assumes that you are upgrading FCKeditor module [M] and FCKeditor (the editor)[E] at the same time. 
Instructions specific for module upgrades are tagged with [M], steps that must be taken when upgrading FCKeditor (the editor) are marked with [E].

   1. [M] Download the latest version of FCKeditor module from http://drupal.org/project/fckeditor (it is advised to read release notes before going further).
   2. [E] Download the latest version of FCKeditor from http://www.fckeditor.net/download (it is advised to read "what's new" before going further: http://www.fckeditor.net/whatsnew).
   3. [M] Back up your database.
   4. [EM] Place the site in "Off-line" mode, to let the database updates run without interruption and avoid displaying errors to end users of the site.
   5. [E] If you have used the FCKeditor built-in file browser, make a backup of sites/all/modules/fckeditor/fckeditor/editor/filemanager/connectors/php/config.php
   6. [E] If you have configured spellchecker, make a backup of sites/all/modules/fckeditor/fckeditor/editor/dialog/fck_spellerpages/spellerpages/server-scripts/spellchecker.php
   7. [E] If you have made any changes inside of sites/all/modules/fckeditor/fckeditor.config.js (or sites/all/modules/fckeditor/fckeditor/fckconfig.js), write down your changes and add them again after uploading new files (e.g. own toolbar definitions, re-enable a plugin etc.). Try to not make any changes to fckconfig.js and add everything to fckeditor.config.js.
   8. Delete old files:
      [EM]* Simply remove modules/fckeditor directory if upgrading both, the editor and the module. 
      [M] If you are upgrading module only, remember to leave the modules/fckeditor/fckeditor directory. 
      [E] When upgrading the editor, remove contents of modules/fckeditor/fckeditor directory only.
      WARNING: if you don't remove old files and just rename fckeditor directory instead e.g. to fckeditor_old, Drupal may use module from the fckeditor_old directory.
   9. [M] Upload FCKeditor module (extracted files and folders) to sites/all/modules directory.
   10. [E] Upload FCKeditor (extracted files and folders from the fckeditor directory) to sites/modules/fckeditor/fckeditor (i.e. where COPY HERE.txt file exists)
   11. [E] Replace the new config.php (see step 5) file with the old one (or RECOMMENDED way: perform again step with adding require_once '../../../../../filemanager.config.php'; to config.php)
   12. [E] Replace the new spellchecker.php with the old one (see step 6) (or RECOMMENDED way: configure new spellchecker.php following the settings from the old file).
   13. [E] Apply your modifications to default configuration in fckeditor.config.js file (see step 7).
   14. [M] If you're using Image Assist module, copy the new img_assist_fckeditor.js to modules/img_assist folder.
   15. [M] Run update.php.
   16. [EM] Put the site back online.

Help & Contribution
-------------------
If you are looking for more information, have any troubles in configuration or if 
you found an issue, please visit the official project page:
  http://drupal.org/project/fckeditor

Having problems? Take a look at list of common problems when installing FCKeditor:
  http://drupal.fckeditor.net/troubleshooting

How to tune up FCKeditor to your theme:
  http://drupal.fckeditor.net/tricks
  
We would like to encourage you to join our team if you can help in any way.
If you can translate FCKeditor module, please use fckeditor.pot file as a template
(located in "po" directory) and send us the translated file so that we could attach it.
Any help is appreciated.
     
Credits
-------
 - FCKeditor for Drupal Core functionality originally written by:
     Frederico Caldeira Knabben
     Jorge Tite (LatPro Inc.)

 - FCKeditor for Drupal 5.x originally written by:
     Ontwerpwerk (www.ontwerpwerk.nl)
 
 - FCKeditor for Drupal 5.x is currently maintained by FCKeditor team.
     http://www.fckeditor.net/

 - FCKeditor - The text editor for internet
     Copyright (C) 2003-2006 Frederico Caldeira Knabben
     http://www.fckeditor.net/

File

README.txt
View source
  1. CONTENTS OF THIS FILE
  2. ---------------------
  3. * Overview
  4. * Required components
  5. * More information and licence
  6. * Requirements
  7. * Configuration
  8. * Installation troubleshooting
  9. * Plugins: Teaser break and Pagebreak
  10. * Uploading images and files
  11. * How to enable the built-in file browser
  12. * Modules: Image Assist
  13. * Modules: Link to content (EXPERIMENTAL)
  14. * Link to content + Path Filter (EXPERIMENTAL)
  15. * Upgrading instructions
  16. * Help & Contribution
  17. * Credits
  18. Overview
  19. --------
  20. This module allows Drupal to replace textarea fields with the
  21. FCKeditor.
  22. This HTML text editor brings many of the powerful functions of known
  23. desktop editors like Word to the web. It's relatively lightweight and
  24. doesn't require any kind of installation on the client computer.
  25. Required components
  26. -------------------
  27. To use FCKeditor in Drupal, you will need to download the FCKeditor
  28. http://www.fckeditor.net/
  29. More information and licence
  30. ----------------------------
  31. FCKeditor - The text editor for internet
  32. Copyright (C) 2003-2006 Frederico Caldeira Knabben
  33. Licensed under the terms of the GNU Lesser General Public License:
  34. http://www.opensource.org/licenses/lgpl-license.php
  35. For further information visit:
  36. http://www.fckeditor.net/
  37. http://drupal.fckeditor.net
  38. Requirements
  39. ------------
  40. - Drupal 5.x
  41. - PHP 4.3.0 or greater
  42. - FCKeditor 2.3.x or greater (http://www.fckeditor.net/)
  43. Configuration
  44. -------------------
  45. 1. Enable the module as usual from Drupal's admin pages.
  46. 2. Grant permissions for use of FCKeditor in Administer > User Management > Access Control
  47. 3. Under Administer > Settings > FCKeditor, create the fckeditor profiles.
  48. In each profile you can choose which textareas will be replaced by FCKeditor,
  49. select default toolbar and configure some more advanced settings
  50. 4. For the Rich Text Editing to work you also need to configure your filters for the users that may access Rich Text Editing.
  51. Either grant those users Full HTML access or use the following:



      1.  
      2. .
      3. 5. To have a better control over line breaks, you may disable Line break converter in the chosen filter (recommended).
      4. 6. Modify the fckeditor.config.js file to custom your needs (optional).
      5. You may copy the needed configuration lines from the default FCKeditor configuration settings (modules/fckeditor/fckeditor/fckconfig.js),
      6. the lines in fckeditor.config.js will override most settings.
      7. WARNING: clear browser's cache after you modify any of the javascript files.
      8. If you don't do this, you may notice that browser is ignoring all your changes.
      9. Installation troubleshooting
      10. ----------------------------
      11. If your FCKeditor does not show you must check if all files are extracted correctly.
      12. The directory /drupal5/modules/fckeditor/fckeditor/ should have the following files:
      13. fckeditor.js, fckconfig.js, fckstyles.xml, fcktemplates.xml, fckeditor.php,
      14. fckeditor_php4.php, fckeditor_php5.php and a directory named editor.
      15. The correct directory structure is as follows:
      16. modules
      17. fckeditor
      18. fckeditor.module
      19. fckeditor
      20. _samples
      21. editor
      22. COPY_HERE.txt
      23. fckconfig.js
      24. ...
      25. If you're still having problems, scroll down to the "Help & Contribution" section.
      26. Plugins: Teaser break and Pagebreak
      27. -----------------------------------
      28. By default, FCKeditor module comes with two plugins that can handle teaser break () and pagebreak ().
      29. You can enable any (or even both) of them.
      30. 1. Open /drupal5/modules/fckeditor/fckeditor.config.js and uncomment these three lines:
      31. FCKConfig.PluginsPath = '../../plugins/' ;
      32. FCKConfig.Plugins.Add( 'drupalbreak' ) ;
      33. FCKConfig.Plugins.Add( 'drupalpagebreak' ) ;
      34. 2. The second step is to add buttons to the toolbar (in the same file).
      35. The button names are: DrupalBreak, DrupalPageBreak.
      36. For example if you have a toolbar with an array of buttons defined as follows:
      37. ['Image','Flash','Table','Rule','SpecialChar']
      38. simply add those two buttons at the end of array:
      39. ['Image','Flash','Table','Rule','SpecialChar', 'DrupalBreak', 'DrupalPageBreak']
      40. (remember about single quotes).
      41. Uploading images and files
      42. --------------------------
      43. There are three ways of uploading files: By using the built-in file browser, by using a module like IMCE or using the core upload module.
      44. How to enable the built-in file browser
      45. ---------------------------------------
      46. The editor gives the end user the flexibility to create a custom file browser that can be integrated on it.
      47. The included file browser allows users to view the content of a specific directory on
      48. the server and add new content to that directory (create folders and upload files).
      49. 1. To enable file browsing you need to edit the connector configuration file in your fckeditor module directory, the file should be in:
      50. /drupal5/modules/fckeditor/fckeditor/editor/filemanager/connectors/php/config.php
      51. (FCKeditor 2.5+)
      52. or
      53. /drupal5/modules/fckeditor/fckeditor/editor/filemanager/browser/default/connectors/php/config.php
      54. and
      55. /drupal5/modules/fckeditor/fckeditor/editor/filemanager/upload/php/config.php
      56. (FCKeditor 2.3.x - 2.4.x)
      57. In this file(s) you will need to enable the file browser by adding one line that includes file with the special authentication function for Drupal (filemanager.config.php). Add this code:
      58. require_once "../../../../../filemanager.config.php";
      59. (FCKeditor 2.5+)
      60. or
      61. require_once "/absolute/path/to/drupal5/modules/fckeditor/filemanager.config.php"
      62. (FCKeditor 2.3.x - 2.4.x)
      63. straight below this line:
      64. $Config['UserFilesAbsolutePath'] = '' ;
      65. The config.php file also holds some other important settings, please take a look at it and adjust it to your needs (optional).
      66. 2. As of Drupal 5.2, additional step is required: locate file named settings.php inside
      67. your drupal directory (usually sites/default/settings.php) and set $cookie_domain variable to the appropriate domain (remember to uncomment that line). If you not do this, FCKeditor will claim that file browser is disabled
      68. 3. Enabling file uploads is a security risk. That's why you have to grant a separate permission to enable the file browser to certain groups.
      69. 4. Lastly, adjust the File browser settings for each profile.
      70. Modules: Image Assist
      71. ---------------------
      72. Image Assist can be integrated with FCKeditor.
      73. To do this, simply copy the modules/fckeditor/img_assist_fckeditor.js file to modules/img_assist/img_assist_fckeditor.js.
      74. Note: this version of the FCKeditor module only supports the 1.x versions of the Image Assist module.
      75. Modules: Link to content (EXPERIMENTAL)
      76. ---------------------------------------
      77. Link to content module can be integrated with FCKeditor.
      78. ATTENTION: this module is not yet compatible with FCKeditor :(
      79. The unofficial version of Link to content module compatible with FCKeditor can be downloaded here:
      80. * 5.x-1.7 (2007-Oct-04)
      81. http://drupal.fckeditor.net/download/linktocontent-fckeditor-5.x-1.7.tar.gz
      82. * 5.x-2.x-dev (2008-Mar-06)
      83. http://drupal.fckeditor.net/download/linktocontent-fckeditor-5.x-2.x-dev.tar.gz
      84. Alternatively, you may apply required changes in the linktocontent code by yourself.
      85. To do this, download the linktocontent module from http://drupal.org/project/linktocontent.
      86. The minimal list of required changes in this module is available here:
      87. http://drupal.fckeditor.net/linktocontent.patch
      88. Installation:
      89. Follow the instruction from INSTALL.txt attached to the linktocontent module.
      90. Then do the following steps to add Linktocontent button to the FCKeditor toolbar:
      91. By default, FCKeditor module comes with two plugins that allows you to use linktocontent and linktonode features.
      92. You can enable any (or even both) of them.
      93. 1. Open /drupal/modules/fckeditor/fckeditor.config.js and uncomment these three lines:
      94. FCKConfig.PluginsPath = '../../plugins/' ;
      95. FCKConfig.Plugins.Add( 'linktonode', 'en,pl' ) ;
      96. FCKConfig.Plugins.Add( 'linktomenu', 'en,pl' ) ;
      97. 2. The second step is to add buttons to the toolbar (in the same file).
      98. The button names are: LinkToNode, LinkToMenu.
      99. For example if you have a toolbar with an array of buttons defined as follows:
      100. ['Link','Unlink','Anchor']
      101. simply add those two buttons at the end of array (or somewhere in the middle):
      102. ['Link','Unlink','LinkToNode','LinkToMenu','Anchor']
      103. (remember about single quotes).
      104. Link to content + Path Filter (EXPERIMENTAL)
      105. --------------------------------------------
      106. Linktonode plugin (read above) is also compatible with Path Filter module.
      107. You can create links to your sites using special syntax: internal:node/23.
      108. Download and install Path Filter module: http://drupal.org/project/pathfilter
      109. Edit your FCKeditor profile:
      110. 1. Go to "Advanced options" section
      111. 2. In "Path Filter & Link To Content integration" choose either
      112. "Link using internal: links" or "Allow user to select between paths and internal links"
      113. Upgrading instructions
      114. ----------------------
      115. This instruction assumes that you are upgrading FCKeditor module [M] and FCKeditor (the editor)[E] at the same time.
      116. Instructions specific for module upgrades are tagged with [M], steps that must be taken when upgrading FCKeditor (the editor) are marked with [E].
      117. 1. [M] Download the latest version of FCKeditor module from http://drupal.org/project/fckeditor (it is advised to read release notes before going further).
      118. 2. [E] Download the latest version of FCKeditor from http://www.fckeditor.net/download (it is advised to read "what's new" before going further: http://www.fckeditor.net/whatsnew).
      119. 3. [M] Back up your database.
      120. 4. [EM] Place the site in "Off-line" mode, to let the database updates run without interruption and avoid displaying errors to end users of the site.
      121. 5. [E] If you have used the FCKeditor built-in file browser, make a backup of sites/all/modules/fckeditor/fckeditor/editor/filemanager/connectors/php/config.php
      122. 6. [E] If you have configured spellchecker, make a backup of sites/all/modules/fckeditor/fckeditor/editor/dialog/fck_spellerpages/spellerpages/server-scripts/spellchecker.php
      123. 7. [E] If you have made any changes inside of sites/all/modules/fckeditor/fckeditor.config.js (or sites/all/modules/fckeditor/fckeditor/fckconfig.js), write down your changes and add them again after uploading new files (e.g. own toolbar definitions, re-enable a plugin etc.). Try to not make any changes to fckconfig.js and add everything to fckeditor.config.js.
      124. 8. Delete old files:
      125. [EM]* Simply remove modules/fckeditor directory if upgrading both, the editor and the module.
      126. [M] If you are upgrading module only, remember to leave the modules/fckeditor/fckeditor directory.
      127. [E] When upgrading the editor, remove contents of modules/fckeditor/fckeditor directory only.
      128. WARNING: if you don't remove old files and just rename fckeditor directory instead e.g. to fckeditor_old, Drupal may use module from the fckeditor_old directory.
      129. 9. [M] Upload FCKeditor module (extracted files and folders) to sites/all/modules directory.
      130. 10. [E] Upload FCKeditor (extracted files and folders from the fckeditor directory) to sites/modules/fckeditor/fckeditor (i.e. where COPY HERE.txt file exists)
      131. 11. [E] Replace the new config.php (see step 5) file with the old one (or RECOMMENDED way: perform again step with adding require_once '../../../../../filemanager.config.php'; to config.php)
      132. 12. [E] Replace the new spellchecker.php with the old one (see step 6) (or RECOMMENDED way: configure new spellchecker.php following the settings from the old file).
      133. 13. [E] Apply your modifications to default configuration in fckeditor.config.js file (see step 7).
      134. 14. [M] If you're using Image Assist module, copy the new img_assist_fckeditor.js to modules/img_assist folder.
      135. 15. [M] Run update.php.
      136. 16. [EM] Put the site back online.
      137. Help & Contribution
      138. -------------------
      139. If you are looking for more information, have any troubles in configuration or if
      140. you found an issue, please visit the official project page:
      141. http://drupal.org/project/fckeditor
      142. Having problems? Take a look at list of common problems when installing FCKeditor:
      143. http://drupal.fckeditor.net/troubleshooting
      144. How to tune up FCKeditor to your theme:
      145. http://drupal.fckeditor.net/tricks
      146. We would like to encourage you to join our team if you can help in any way.
      147. If you can translate FCKeditor module, please use fckeditor.pot file as a template
      148. (located in "po" directory) and send us the translated file so that we could attach it.
      149. Any help is appreciated.
      150. Credits
      151. -------
      152. - FCKeditor for Drupal Core functionality originally written by:
      153. Frederico Caldeira Knabben
      154. Jorge Tite (LatPro Inc.)
      155. - FCKeditor for Drupal 5.x originally written by:
      156. Ontwerpwerk (www.ontwerpwerk.nl)
      157. - FCKeditor for Drupal 5.x is currently maintained by FCKeditor team.
      158. http://www.fckeditor.net/
      159. - FCKeditor - The text editor for internet
      160. Copyright (C) 2003-2006 Frederico Caldeira Knabben
      161. http://www.fckeditor.net/