Forgot your password?
New user?
Document Actions
RichDocument
Category: Layout and presentation
—
Other products by this author
Current release: RichDocument 3.0.1
Released Sep 28, 2007 — tested with Plone 3.0
A bugfix release for Plone 3
Experimental releases
Upcoming and alpha/beta/candidate releases
- Alpha releases should only be used for testing and development.
- Beta releases and Release Candidates are normally released for production testing, but should not be used on mission-critical sites.
- Always install on a separate test server first, and make sure you have proper backups before installing.
Release roadmap for RichDocument…
Project Description
- Project resources
Releases
Issue tracker
Roadmap
Code repositoryby Martin Aspeli
RichDocument is a document type which provies the same fields as the standard Plone Document/Page type, but allows users to upload images directly into the document during editing.
A RichDocument is a folderish type with Image and File as the only permitted contained types. Two special widgets for managing contained images and attachments are provided near the bottomf of the edit form, though you have to expand a collapsed fieldset to see them.
Once uploaded, images and attachments can be referenced in the document's body text or inserted using editors such as kupu.
In addition, the user can optionally either automatically float the topmost uploaded image at the top left of the page, or display a box of thumbnails floating at the right of the page, on which the viewer can click to open the full-size image in a pop-up window. This is achieved using the Plone 2.1 "display" menu.
RichDocument is released under the GNU General Public Licence, version 2. Please see http://gnu.org for more details.
Installation
Install in the usual way, using the QuickInstaller.
Acknowlegements
The ImagesManagerWidget was originally created for km|portal, a knowledge management system aimed at small businesses (c) 2004 Martin Aspeli.
Known Issues and Potential Improvements
- The user interface is not internationalised. Patches to provide i18n keys and translations welcome!
- It's not possible to upload images while the object is still in the portal_factory. If the object is in the factory while it is being edited for the first time and the user uploads an image, it will be instantiated into the target folder first.
- The image and attachment controls are submit buttons, managed via PortalFormController with custom actions registered during the installation. However, this button comes before the Save button on the form, and thus may steal the default button status - if the user presses Enter in the form, they may get a (benevolent) portal error message telling them they must upload an image.
- The only re-ordering support provided directly by the manager widgets is "move to top". This is useful in support of the single-image preview mode or to make an attachment in the attachments download box stand out, but more detailed re-ordering functionality may be desirable.
