Plone ONLYOFFICE integration plugin

This plugin allows users to edit office documents within Plone using ONLYOFFICE Document Server - Community or Integration Edition.

The plugin allows to:

  • Create and edit text documents, spreadsheets, and presentations.
  • Share documents with other users.
  • Co-edit documents in real-time: use two co-editing modes (Fast and Strict), Track Changes, comments, and built-in chat.

Supported formats:

  • For viewing and editing: DOCX, XLSX, PPTX.
  • For viewing only: PDF, ODT, ODS, ODP, DOC, XLS, PPT.

You will need an instance of ONLYOFFICE Document Server that is resolvable and connectable both from Plone and any end-clients. ONLYOFFICE Document Server must also be able to POST to Plone directly.

You can install free Community version of ONLYOFFICE Document Server or scalable enterprise-level Integration Edition.

To install free Community version, use Docker (recommended) or follow these instructions for Debian, Ubuntu, or derivatives.

To install Integration Edition, follow instructions here.

  1. Install plugin by adding it to your buildout.cfg: [buildout] ... eggs = onlyoffice.connector
  2. Run bin/buildout.
  3. Go to Site Setup -> Add-ons and press the Install button to enable plugin.

You could also install plugin via Docker:

docker run --rm -p 8080:8080 -e ADDONS="onlyoffice.connector" plone

Both options will automatically install plugin from PyPi.

To configure plugin go to Site Setup. Scroll down to Add-ons Configuration section and press the ONLYOFFICE Configuration button.

  1. Clone repository and change directory: git clone --branch deploy cd onlyoffice-plone
  2. Create a virtualenv in the package.
  3. Install requirements with pip.
  4. Run buildout: virtualenv . ./bin/pip install -r requirements.txt ./bin/buildout
  5. Start Plone in foreground: ./bin/instance fg

If you have a working Plone instance, you can install plugin by adding the project files to the scr directory:

  1. In the scr directory create the onlyoffice.connector directory.
  2. Put your project files received by git into the onlyoffice.connector directory.
  3. Edit the buildout.cfg file: [buildout] ... eggs = onlyoffice.connector develop = src/onlyoffice.connector
  4. Rerun buildout for the changes to take effect: .bin/buildout
  5. Then start or restart your Plone instance.

Note that Plone is based on Zope server and will not run as root user. If you intend to run it as root user. You must supply effective-user directive. In order to do so add effective-user <username> line to ./parts/instance/etc/zope.conf.

  1. If you specified a concrete plugin version in your buildout.cfg file (so-called pinning, and a recommended practice), like onlyoffice.connector = 1.0.0, update this reference to point to the newer version. If the plugin version is not specified, then the latest version will be automatically loaded: [versions] ... onlyoffice.connector = 1.0.1
  2. Run bin/buildout. Wait until the new version is downloaded and installed.
  3. Restart Plone - your site may look weird, or even be inaccessible until you have performed the next step.
  4. Navigate to the Add-on screen (add /prefs_install_products_form to your site URL) and in the Upgrades list select onlyoffice.connector and click Upgrade onlyoffice.connector.

The ONLYOFFICE integration follows the API documented here:

  • User navigates to a document within Plone and selects the ONLYOFFICE Edit action.
  • Plone prepares a JSON object for the Document Server with the following properties:
    • url: the URL that ONLYOFFICE Document Server uses to download the document;
    • callbackUrl: the URL that ONLYOFFICE Document Server informs about status of the document editing;
    • key: the UUID+Modified Timestamp to instruct ONLYOFFICE Document Server whether to download the document again or not;
    • title: the document Title (name).
  • Plone constructs a page from a .pt template, filling in all of those values so that the client browser can load up the editor.
  • The client browser makes a request for the javascript library from ONLYOFFICE Document Server and sends ONLYOFFICE Document Server the docEditor configuration with the above properties.
  • Then ONLYOFFICE Document Server downloads the document from Plone and the user begins editing.
  • ONLYOFFICE Document Server sends a POST request to the callback URL to inform Plone that a user is editing the document.
  • When all users and client browsers are done with editing, they close the editing window.
  • After 10 seconds of inactivity, ONLYOFFICE Document Server sends a POST to the callback URL letting Plone know that the clients have finished editing the document and closed it.
  • Plone downloads the new version of the document, replacing the old one.