-- edit your *buildout.cfg* - add *pp.client.plone* to the
- **eggs** options of your buildout.cfg:
+- edit your *buildout.cfg* - add *pp.client-plone* to the
+ **eggs** options of your buildout.cfg::
-- When running the Produce & Publish server on a different server, you must
- adjust the ``PP_SERVER`` environment variables within your
- *.bashrc* file (or a similar file) or you put those variables into your
- buildout configuration using the *<environment>* section. Username and
- password are only needed when you run the Produce & Publish server behind a
- reverse proxy (requiring authentcation).
+- When running the Produce & Publish server on a different server, you must
+ adjust the ``PP_SERVER`` environment variables within your *.bashrc* file (or
+ a similar file) or you put those variables into your buildout configuration
+ using the *<environment>* section. Username and password are only needed
+ when you run the Produce & Publish server behind a reverse proxy (requiring
+.. note:: This version of the Produce & Publish Plone Client Connector
+ requires an installation of the new ``pp.server`` Produce & Publish Server.
+ It will not work with the older ``zopyx.smartprintng.server`` server implementation.
Supported Plone content-types
-- Folder (nested structure)
+- Folder (nested structure)
+- Collection (new-style collections Plone 4.3 only)
+There is no direct support for Dexterity content-types available however the
+configuration contains an example configuration on how to register the
+interface of a Dexterity content-type with the Plone Client Connector. However
+support for Dexterity types will only work for filesystem-based Dexterity types
+with a related marker interface - there is no support for through-the-web
+defined Dexterity types.
The Plone connector provides a dedicated @@asPDF view that can
be added to the URL of any of the supported content-types of Plone
(Document, Folder, Newsitem, PloneGlossary). So when your document
-is for example associated with the URL
+is for example associated with the URL