Plug-ins"

This website contains links to software which is either no longer maintained or will be supported only until the end of 2019 (CKFinder 2). For the latest documentation about current CKSource projects, including software like CKEditor 4/CKEditor 5, CKFinder 3, Cloud Services, Letters, Accessibility Checker, please visit the new documentation website.

If you look for an information about very old versions of CKEditor, FCKeditor and CKFinder check also the CKEditor forum, which was closed in 2015. If not, please head to StackOverflow for support.

(New page: == Creating & Installing a Plugin in FCKeditor == === Writing a plugin === The directory structure for a plugin must always follow the same pattern. The plugin directory must have the sa...)
(No difference)

Revision as of 10:49, 17 January 2008

Creating & Installing a Plugin in FCKeditor

Writing a plugin

The directory structure for a plugin must always follow the same pattern. The plugin directory must have the same name as the plugin and it must contain a fckplugin.js file. It may also optionally include a language directory with various localized language definitions for your Users Interface (UI). Each file defines a single language, and the filenames (without .js) are what should be passed to FCKConfig.Plugins.Add (see below). If your command has no UI then you don't need to supply any language files.

For the 'findreplace' plugin the structure would look like this (assuming the default plugin path is editor/plugins/): 

/editor/plugins/findreplace/fckplugin.js
/editor/plugins/findreplace/lang/en.js
/editor/plugins/findreplace/lang/it.js
Retrieved from "https://docs-old.ckeditor.com/index.php?title=FCKeditor_2.x/Developers_Guide/Customization/Plug-ins&oldid=1707"