(Article contents proof-read and formatted) |
(Minimum Setup section added) |
||
Line 34: | Line 34: | ||
For example:<br /> | For example:<br /> | ||
<code><nowiki>http://www.example.com/ckeditor/_samples/index.html</nowiki></code> | <code><nowiki>http://www.example.com/ckeditor/_samples/index.html</nowiki></code> | ||
+ | |||
+ | == Minimum Setup == | ||
+ | You probably do not need to use all of the files from the CKEditor installation package on a production server, so you can go through the list below and manually remove some of them according to your needs. | ||
+ | * <code>_ samples</code> — this directory contains CKEditor samples. Using the sample files is the easiest way to verify whether your setup works properly. If CKEditor works correctly, you can safely remove the whole <code>_ samples</code> folder. | ||
+ | * <code>_ source</code> — this directory contains CKEditor source code. It is needed only if you intend to use the <code>ckeditor_source.js</code> script and load CKEditor from source files. | ||
+ | * <code>adapters</code> — this directory contains CKEditor adapters. It may be removed if you do not use any adapters, like the [[CKEditor 3.x/Developers Guide/jQuery Adapter|jQuery]] one. | ||
+ | * <code>images</code> — this directory contains CKEditor graphics files. It is necessary for CKEditor to work. | ||
+ | * <code>lang</code> — this directory contains CKEditor language files. It is necessary for CKEditor to work, although you can remove the unused language files if you force the CKEditor interface language using the <code>[http://docs.cksource.com/ckeditor_api/symbols/CKEDITOR.config.html#.language CKEDITOR.config.language]</code> property set in the <code>config.js</code> file or limit the number of languages available using the <code>[http://docs.cksource.com/ckeditor_api/symbols/CKEDITOR.lang.html#.languages CKEDITOR.lang.languages]</code> setting from the <code>core/lang.js</code> file. | ||
+ | * <code>plugins</code> — this directory contains the plugin files and is necessary for CKEditor to work. Due to the modular construction of the editor some core functionality was delegated to plugins. You can remove some unused plugins that are not packed in <code>ckeditor.js</code> (and thus listed in the <code>ckeditor.pack</code> file) and are only loaded on demand through the [http://docs.cksource.com/ckeditor_api/symbols/CKEDITOR.config.html#.extraPlugins CKEDITOR.config.extraPlugins] property. | ||
+ | * <code>skins</code> — this directory contains CKEditor skin files along with toolbar buttons and stylesheet definitions and is necessary for CKEditor to work. You can however remove unused skins and their files. | ||
+ | * <code>themes</code> — is necessary for CKEditor to work. | ||
+ | |||
+ | From the CKEditor root directory you can safely remove the following files: | ||
+ | * <code>CHANGES.html</code> | ||
+ | * All <code>.asp</code> files. | ||
+ | * All <code>.php</code> files. | ||
+ | * <code>ckeditor.pack</code> | ||
+ | * <code>ckeditor_basic.js</code> and <code>ckeditor_basic_source.js</code> files (if you do not use this method for loading CKEditor) | ||
+ | * <code>ckeditor_source.js</code> (if you do not use this method for loading CKEditor) | ||
+ | * <code>INSTALL.html</code> |
Revision as of 11:18, 4 January 2011
Contents
Installing CKEditor is easy. In order to install the editor, choose an appropriate procedure (fresh install or upgrade) and follow the steps described below.
Installation Procedures
Fresh Installation
To install CKEditor for the first time, proceed in the following way:
- Download the latest version of the editor from our website: http://ckeditor.com/download
- Extract (decompress) the downloaded archive to a directory called
ckeditor
in the root of your website.
Upgrade
To upgrade an existing CKEditor installation, proceed in the following way:
- Rename your old editor folder to a backup folder, for example
ckeditor_old
. - Download the latest version of the editor from our website: http://ckeditor.com/download
- Extract (decompress) the downloaded archive to the original editor directory, for example
ckeditor
. - Copy all configuration files that you have changed from the backup folder to their corresponding position in the new directory. These could include (but do not have to be limited to) the following files:
-
config.js
-
content.css
-
plugins/templates/templates/default.js
-
plugins/styles/styles/default.js
-
plugins/styles/styles/default.js
-
plugins/pastefromword/filter/default.js
-
Verification of the Installation
CKEditor comes with a few sample pages that can be used to verify that installation proceeded properly. In order to see whether the editor is working, take a look at the _samples
directory.
To test your installation, call the following page at your website:
http://<your site>/<CKEditor installation path>/_samples/index.html
For example:
http://www.example.com/ckeditor/_samples/index.html
Minimum Setup
You probably do not need to use all of the files from the CKEditor installation package on a production server, so you can go through the list below and manually remove some of them according to your needs.
-
_ samples
— this directory contains CKEditor samples. Using the sample files is the easiest way to verify whether your setup works properly. If CKEditor works correctly, you can safely remove the whole_ samples
folder. -
_ source
— this directory contains CKEditor source code. It is needed only if you intend to use theckeditor_source.js
script and load CKEditor from source files. -
adapters
— this directory contains CKEditor adapters. It may be removed if you do not use any adapters, like the jQuery one. -
images
— this directory contains CKEditor graphics files. It is necessary for CKEditor to work. -
lang
— this directory contains CKEditor language files. It is necessary for CKEditor to work, although you can remove the unused language files if you force the CKEditor interface language using theCKEDITOR.config.language
property set in theconfig.js
file or limit the number of languages available using theCKEDITOR.lang.languages
setting from thecore/lang.js
file. -
plugins
— this directory contains the plugin files and is necessary for CKEditor to work. Due to the modular construction of the editor some core functionality was delegated to plugins. You can remove some unused plugins that are not packed inckeditor.js
(and thus listed in theckeditor.pack
file) and are only loaded on demand through the CKEDITOR.config.extraPlugins property. -
skins
— this directory contains CKEditor skin files along with toolbar buttons and stylesheet definitions and is necessary for CKEditor to work. You can however remove unused skins and their files. -
themes
— is necessary for CKEditor to work.
From the CKEditor root directory you can safely remove the following files:
-
CHANGES.html
- All
.asp
files. - All
.php
files. -
ckeditor.pack
-
ckeditor_basic.js
andckeditor_basic_source.js
files (if you do not use this method for loading CKEditor) -
ckeditor_source.js
(if you do not use this method for loading CKEditor) -
INSTALL.html