This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Project Description

LAST CHANGES :

Changes in SVN (Unreleased) :

  1. fix resolveuid links portal transform rule (all links attributes were tranformed in lower case)

Changes in FCK.Plone 2.6.6 - last fixes (**) :

  1. Use FCKEditor 2.6.6 All infos here : http://ckeditor.com/blog/FCKeditor_2.6.6_released
  2. Fix path error for images preview since ISiteRoot is used http://plone.org/products/fckeditor/issues/71

Changes in FCK.Plone 2.6.5.2 - last fixes (**) :

  1. Fix path error when link by uid is not used http://plone.org/products/fckeditor/issues/68 http://plone.org/products/fckeditor/issues/69
  2. Fix path error when using direct upload (when linkbyuid is not used)

Changes in FCK.Plone 2.6.5.1 - last fixes (**) :

  1. Added the ability to change browser path and browser root with a contextual method
  2. Force FCKeditor when fckwidget is used in a field
  3. Fix fckeditor browser root to the first parent which provides INavigationRoot
  4. Added fck_area_css_id and fck_area_css_class attributes in fckwidget to be able to get real wysiwyg when editing zones outside of #content (ex #portal-footer or something else)

(**) FCKeditor 2.x will be replaced by CKeditor 3.x in near future

Changes in FCK.Plone 2.6.5 :

  1. Includes FCKeditor 2.6.5 version (see docs/_whatsnew.html)
  2. Includes imgmap plugin (http://martinezdelizarrondo.com/imagemaps/) a very good tool
  3. If a folder had not the same skin as portal, this skin was not rendered in FCKeditor area because the skinname was missing in css urls in getFCKArea_default_style.py
  4. The default opening folder for upload is no more the Article but the parent when editing PloneArticle content types. Fix the ‘upload not allowed error’ when using the quick upload feature.

README :

Introduction

This product is a FCKEditor Plone integration. will be replaced in near future by a new package collective.ckeditor currently available on svn only (developpement state)

For more information read documentation inside product :
  • “docs” folder contains all documentation
  • “_whatsnew.html”, “_documentation.html” and “_upgrade.html” contain informations about the original FCKEditor product.

FCKeditor.Plone 2.6.6 - Plone product installation

FCKeditor.Plone 2.6.6 is based on FCKeditor 2.6.6 original code source. This package is Plone 3.xx and Plone 2.5.x compatible Since 2.4.3, Plone3 kss rich content edition is fully supported.

Read docs/INSTALL.txt

Go to your Plone Site > Plone Control Panel > Add Remove Products, Choose FCKeditor … or use Portal_QuickInstaller inside ZMI.

Then read docs/FAQ.txt

Upgrade : read the upgrade help in docs/FAQ.txt

download + install from SVN: read docs/SVN.txt (important)

Support

support@ingeniweb.com

Plone project page (infos, tracker, download …) : http://plone.org/products/fckeditor

Issues Tracker : http://trac.ingeniweb.com

For more information about original editor:

FCK Editor web site : http://fckeditor.net/ FCK Editor dev trac : http://dev.fckeditor.net/

FCKEditor Plone Help :

I. FCKeditor.Plone upgrade

  • Uninstall FCK editor from your Plone site (Quick Installer or Plone Control Panel)
  • Delete FCKeditor directory from your_instance/Products directory if exists (for versions < 2.6)
  • Read INSTALL.txt for buildout installation or how to use easy_install
  • Restart Zope
  • Install FCKeditor.Plone in your Plone Site via QuickInstaller or Plone Control Panel
  • Configure FCKeditor through the Plone control panel.

FCK_PROPERTIES :

When upgrading from FCKeditor.Plone >= 2.2.x fckeditor plone properties are preserved after install/uninstall but if you want, you can clean it (recommanded) : ZMI > your site > portal_properties - delete fckeditor_properties

Since FCKEditor.Plone 2.3.2 spellCheck properties have changed, if you have customized your toolbar, change “SpellCheck” in “rtSpellCheck” for ff2+ and MSIE6+ client spellchecker. If you were using aspell server spellchecker, it’s not required.

Since FCKEditor.Plone 2.3.3 “FitWindow” button has been added to switch editor field in fullscreen mode, if you have customized your toolbar, add ‘FitWindow’ in your customized toolbar.

Since FCKEditor.Plone 2.4.1 “UniversalKey” function has been removed, if you have customized your toolbar, remove ‘UniversalKey’ from your customized toolbar.

Since FCKEditor.Plone 2.4.3 “UniversalKey” function has been re-added as optional plugin, you can add ‘UniversalKey’ in your customized toolbar.

Since FCKEditor.Plone 2.4.3 new important properties have been added, so deleting fckeditor_properties is highly recommanded (just rename it and you would be able to copy/paste by hand some of your customized properties)

Since FCKEditor.Plone 2.6 one property have been removed : “gecko_uses_span” (no more useful because IE doesn’t use Font tag anymore)

Since FCKEditor.Plone 2.6.5 imagemap plugin has been added in default custom toolbar, add the ‘imgmapPopup’ button to your own custom toolbar.

Since FCKEditor.Plone 2.6.5.1 two new important properties have been added, fck_force_other_path_method and fck_force_other_root_method deleting fckeditor_properties before reinstalling product is recommanded, otherwise you could get many errors.

CACHE :

Use CacheFu to get better performances, or at least, just change standard Plone HTTPCache params (unselect anonymous only is really important !!!).

Upgrade from old FCK.Plone versions (<=2.2) :

  • Delete all previous specific FCKeditor ZMI customizations,
  • You could need to upgrade your members wysiwyg_editor property in your portal_membership (this property has changed since FCKeditor.Plone 2.0.1 for easy cohabitation with Kupu and Epoz), follow these steps :
    • In your Plone site ZMI > create an External Method Id : updateFckUsers Title : updateFckUsers Module Name : FCKeditor.updateFckUsers Function Name : updateFckUsers
    • Click on test
    • Your portal_membership is updated

II. FCKeditor.Plone Update from svn

If you have downloaded FCKeditor.Plone from Plone collective SVN, launch utils/base2zope.py at python prompt, before installation, it’s a mandatory.

III. FAQ

  1. How to enable flash publication with Plone ? ZMI > your Plone Site > portal_transforms > safe_html Add “embed” tag (value=1) in valid_tags Remove “embed” tag from nasty_tags Restart your instance.

  2. How to enable font color/size modifications ? Go to fckeditor controlpanel, choose custom toolbar and choose to enable fonts and colors.

  3. How to enable javascript events publication (popups, onclick, onmouseover …) with Plone 2.1 ? ZMI > your Plone Site > portal_transforms > safe_html set remove_javascript to 0 This does not effect <script> tags Restart your instance. It’s not recommanded

  4. How to disable file and/or image and/or flash upload ? Set this option in FCKEditor Plone Control Panel

  5. How To change default style in editor windows ? css from portal_css are used by default. You can set your own css with FCKEditor Plone Control Panel (useful with Deliverance)

  6. How To change toolbars set ? with FCKEditor Plone Control Panel

  7. How To Force Paste as Plain Text when copy-paste from rich-text document ? choose this option with FCKEditor Plone Control Panel

  8. How to disable unique ID referencing when browsing server AT Content Types and Plone 2.1 standard Content types ? Use the FCKeditor Plone Control Panel

  9. How to publish absolute links ? Nothing to do. In editor and after page saving, all internal links are stored as “unik id” links, but these links are transformed in absolute urls by Plone portal_transforms when displaying the page for a simple view.

  10. How to use your custom styles in the editor area and combo menu ? In the FCKeditor Plone Control Panel Modify the field “FCK Editor Styles List” If you want to use css classes or ids you need to check up your plone styles

  11. How to set FCK Editor as default editor for all new members in your Plone site : - Go in ZMI > Your Site > portal_member_data > properties - In the field “wysiwyg_editor” enter “FCKeditor” - submit the form

  12. How to force the Member personal folder as opening folder in browser and for fast upload ? Choose this option in FCKeditor Plone Control Panel

  13. How to force the browser’s root to Member personnal folder ? If you follow the step 9, the user will use his personnal folder for fast upload and the browser will be open in this folder, but the user is still able to browse all site published contents. You can set the browser root if you want :

    To force the browser root to Member personal Folder : choose this option in FCKeditor Plone Control Panel

  14. How to force browser path or browser root to a particular folder ? Choose it in the FCKeditor Plone Control Panel

  15. How does FireFox 2.0 spellchecker work ? End User must click on spellchecker icon. End User must install and choose dictionnary for his language by right clicking in fckeditor area or another form text area. When spellcheck icon is enable in FCK bad words are red underlined Now, user can replace/add to dictionnary …. in editor area. FireFox spellchecker is really powerful feature, advise authors to use FireFox ;-)

  16. How to change portal_types used for file/image/flash upload ? Choose it in the FCKeditor Plone Control Panel

  17. How To make FCKeditor able to browse inside my specific PloneArticle based types ? Choose your Plone Article meta_types in FCKEditor Control Panel.

  18. Why did you get many errors after upgrading FCKeditor.Plone (content disappearing, js errors, editor disappearing …)? Read carefully $ I

  19. How to get different FCKeditor configurations for different fields in my own AT Content Types ? Use FCKWidget for your fields (see RichContentDemo.py for an example)

  20. How to make FCKeditor.Plone working without kss : just add fck_ploneInit.js in portal_javascripts with standard options

  21. How to use flvPlayer plugin (at your own risk - not recommanded) : - add ‘flvPlayer’ button in custom toolbar - remove script tags from nasty tags in portal_transforms > safe_html - add script tag as valid tags in portal_transforms > safe_html

  22. How to use the WebSpellChecker provided by www.spellchecker.net ? Choose the WSC option in FCKeditor Plone Control Panel

  23. How to add imgmap plugin ? Just add ‘imgmapPopup’ in your custom toolbar in CKeditor area

  24. How to add a new plugin (GoogleMaps, Advanced Gecko SpellChecker, etc …) to FCKeditor.Plone ? Download the plugin folder in Products/FCKeditor/_addons/plugins directory Launch Products/FCKeditor/utils/base2zope.py at Python prompt, reply ‘y’ to reconstruct the folder ‘fckeditor’ Restart your instance.

IV. SUPPORT OPEN SOURCE

You want the last fckeditor version for Plone ? You need new plugins or features ? You need more support ?

It’s easy, send an email to support@ingeniweb.com, we will explain you how to support our work and how we could maintain this product together.

V. CONTACTS

support@ingeniweb.com for Plone Product

http://fckeditor.net/ for the fckeditor source

TODO :

Roadmap - 2009/12/28

  • collective.ckeditor 3.x release (complete refactoring with the new ckeditor 3)
  • collective.plonefinder (a new browser for collective.ckeditor which can be used by any html editor)

These works are started on svn, to test it read :

You need to build a develop buildout.

Don’t use it on production sites for now.

All contributions are welcome for these works.

Release History

Release History

2.6.6.3

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

2.6.6.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

2.6.6.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

2.6.6

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

2.6.5.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

2.6.5.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

2.6.5

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

2.6.4.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

2.6.4.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

2.6.4

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

2.6.3.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

2.6.3.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

2.6.3

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

2.6.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

2.6.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

2.6

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
Products.FCKeditor-2.6.6.3.zip (3.9 MB) Copy SHA256 Checksum SHA256 Source Apr 18, 2011

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting