History of FckeditorPackage
Version 13 | Current version | |||||
---|---|---|---|---|---|---|
FCKeditorPackageIntegrated into bitweaver comes FCKeditor, a WYSIWYG editor from fckeditor.net. (See also TinyMCE package.) Features
NOTE: FCKeditor is currently NOT compatible with the Ajax Comments feature in LibertyPackage. ToolbarsBitweaver includes the ability to use one of several toolbars with FCKeditor easily. It is also possible to customize the toolbar by editing the fckeditor/jscripts/fckconfig.js file to specify your own and then adding it to fckeditor/admin/admin_fckeditor_inc.php.SkinsBitweaver includes the ability to skin the interface with one of the three default skins. It is also possible to create your own skin. You will have to add it to the fckeditor/admin/admin_fckeditor_inc.php file to add it to the administration interface.Your own plugins for FCKeditorIf you want to write your own plugin for FCKeditor, here are two good tutorials to get you started:
bitweaver's Plugins for FCKeditorSplitThe Split plugin gives you a button that will insert a split tag: ...split... into your content. This is good for blog posts and articles where you want to easily define a read more section. Now your users don't need to know how to use ...split... they can just click the "Insert Split" button, which includes a hover tool tip letting you know it is for adding a Read More section. To enable Split in your FCKeditor, open the file fckconfig.js and uncomment the following line:/fckeditor/jscripts/fckconfig.js
Now you need to add Split to your toolbar list, for example like: /fckeditor/jscripts/fckconfig.js
AttachmentThe Attachment plugin integrates bitweaver's native LibertyAttachments features into the FCKeditor. Note that the current state of the Attachment plugin only supports previewing of images, and does not yet create attachment associations between content and uploaded files. Like the attachment tab in most liberty content packages this FCK plugin will let you upload files via Ajax to associate with your user account. You can also get a list of all attachments your user has ever uploaded. From the resulting list it is a single click to insert attachment code into your text. The FCK plugin will also preview the attachment image in the FCK editing interface. To enable Attachment in your FCKeditor you need to edit fckconfig.js and FCKeditor's header_inc.tpl:/fckeditor/jscripts/fckconfig.js
Now you need to add Attachment to your toolbar list, for example like: /fckeditor/jscripts/fckconfig.js
Finally, include a number of the MochiKit Javascript library files: /fckeditor/templates/header_inc.tpl
Image Browser FixTo get the Resources Browser (Image > Browse Server) working so you can upload files, flash, images and media, first change 'asp' to 'php' in fckconfig.js:/fckeditor/jscripts/editor/fckconfig.js
Now create new directories in your storage directory: new directories
Now edit the config.php of FCKeditor's Filemanager: /fckeditor/jscripts/editor/filemanager/browser/default/connectors/php/config.php
Make sure apache can write to the directories you created above: command line
Now point your browser to fckconfig.js (http://localhost/bitweaver/fckeditor/jscripts/fckconfig.js) and hit reload to makes sure that your changes are present in your browser. Custom configuration filesBy setting up your FCKeditor with a custom fckconfig.js, updates become less problematic, and playing around with different settings becomes easier:
Now, of course, create the file fckconfig.js in the path mentioned above. Copy desired variables from their documentation pages. Now if the FCKeditor package is updated, your settings are not lost. FCKeditor's own fckconfig.js stays where it is, the settings of both files are considered automatically. To take it even one step further, externalize the XML file that holds FCK's styles. Copy the file fckstyles.xml from /fckeditor/jscripts/fckstyles.xml to your custom theme. Now you can control what FCK's style drop down looks like to the user. For example, your fckconfig.js file might look like this:
How to use a real Text_Diff (and UTF-8)If you're using the HTML format and also sometimes the WYSIWYG editor and still want to compare different versions of a Wiki page efficiently, you want Text_Diff, the PEAR package that should be installed on your system. There are only 2 problems. First, to make Text_Diff work in a UTF-8 (e.g., non English) environment, you need to stop FCKeditor from processing special characters, otherwise Text_Diff will always find that Motörhead is something else than Motörhead. For that, the last 4 variables in that code sample above need to be uncommented. Next, in /wiki/templates/page_history.tpl around line 40:/wiki/templates/page_history.tpl
Both can be desirable, but the latter version renders HTML, so that Text_Diff'ing might not result in an exact view of all characters that have actually changed, but in a nicy-fied view of what content has actually changed:
How to prevent the FCKifying of certain textareasThere are quite a few textareas that should not be FCKified even if the editor is supposed to be available in general. Examples would be the textarea to add trackback URLs to a blog posting and many of the kernel's textareas. To prevent the editor to hook on to your textareas, don't use bitweaver's "textarea" Smarty-plugin, but normal plain HTML:somepackage/templates/some.tpl
| FCKEditor has been renamed by CKEditor from Version 3. Currently version 3.3.1 is available in bitweaver HEAD. FCKeditorFCKeditor is a rich text editor. This means, input areas for content will look like an Office program. Users mark some text, then click on a button B or hit Ctrl+B on their keyboard, and instantly see the marked text bold. It is browser independent, written in Javascript, and released as Open Source by fckeditor.net. Alternatively, you can use TinyMCE, another rich text editor that can easily be integrated with Bitweaver.How to enable FCKeditor in Bitweaver
Features
ToolbarsBitweaver includes the ability to use one of several toolbars with FCKeditor easily. It is also possible to customize the toolbar by editing the fckeditor/jscripts/fckconfig.js file to specify your own and then adding it to fckeditor/admin/admin_fckeditor_inc.php.SkinsBitweaver includes the ability to skin the interface with one of the three default skins. It is also possible to create your own skin. You will have to add it to the fckeditor/admin/admin_fckeditor_inc.php file to add it to the administration interface.Issues
Your own plugins for FCKeditorIf you want to write your own plugin for FCKeditor, here are two good tutorials to get you started:
Bitweaver's plugins for FCKeditorSplitThe Split plugin gives you a button that will insert a split tag: ...split... into your content. This is good for blog posts and articles where you want to easily define a read more section. Now your users don't need to know how to use ...split... they can just click the "Insert Split" button, which includes a hover tool tip letting you know it is for adding a Read More section. To enable Split in your FCKeditor, open the file fckconfig.js and uncomment the following line:/fckeditor/jscripts/fckconfig.js
Now you need to add Split to your toolbar list, for example like: /fckeditor/jscripts/fckconfig.js
AttachmentThe Attachment plugin integrates bitweaver's native LibertyAttachments features into the FCKeditor. Note that the current state of the Attachment plugin only supports previewing of images, and does not yet create attachment associations between content and uploaded files. Like the attachment tab in most liberty content packages this FCKeditor plugin will let you upload files via Ajax to associate with your user account. You can also get a list of all attachments your user has ever uploaded. From the resulting list it is a single click to insert attachment code into your text. The FCKeditor plugin will also preview the attachment image in the FCKeditor editing interface. To enable Attachment in your FCKeditor you need to edit fckconfig.js and FCKeditor's header_inc.tpl:/fckeditor/jscripts/fckconfig.js
Now you need to add Attachment to your toolbar list, for example like: /fckeditor/jscripts/fckconfig.js
Finally, include a number of the MochiKit Javascript library files, there are two ways to do this. You can add them in the header_inc.tpl or even better is to edit bit_setup_inc.php and include them via our javascript bundling function: /fckeditor/templates/header_inc.tpl
/fckeditor/bit_setup_inc.php
Image Browser FixTo get the Resources Browser (Image > Browse Server) working so you can upload files, flash, images and media, first change 'asp' to 'php' in fckconfig.js:/fckeditor/jscripts/editor/fckconfig.js
Now create new directories in your storage directory: new directories
Now edit the config.php of FCKeditor's Filemanager: /fckeditor/jscripts/editor/filemanager/browser/default/connectors/php/config.php
Make sure apache can write to the directories you created above: command line
Now point your browser to fckconfig.js (http://localhost/bitweaver/fckeditor/jscripts/fckconfig.js) and hit reload to makes sure that your changes are present in your browser. Custom configuration filesSet up your FCKeditor with a custom fckconfig.js to make updates and trying different settings easier:
How to prevent the FCKifying of certain textareasThere are quite a few textareas that should not be FCKified even if the editor is supposed to be available in general. Examples would be the textarea to add trackback URLs to a blog posting and many of the kernel's textareas. To prevent the editor to hook on to your textareas, don't use bitweaver's "textarea" Smarty-plugin, but normal plain HTML:somepackage/templates/some.tpl
|