Noramlly this is a simple matter of apt-get install plone-site
. However, one time I got a half-broken installation with empty /var/lib/zope*/instance
directory. A result of which was failure during Zope startup, due to having no instances. The fix:
dzhandle -z2.9 make-instance plone-site -m manual dzhandle -z2.9 add-product plone-site CMFPlone /etc/init.d/zope2.9 restart
The above steps generate a brand new Zope instance in /var/lib/zope2.9/instance/plone-site
. The configuration file for the instance will be in /etc/zope2.9/plone-site/zope.conf
, you might want to change HTTPPORT from 9673 to 8081, the ubuntu default.
Example: In the registration form for new users, the default message for the password entry is simply "Minimum 5 characters". Let's say we want to change this to "Minimum 5 characters, make sure to choose something others cannot guess and you can remember".
- Go to the Zope management interface of your plone site. (Either from the preferences page or change the URL to end with
/manage
.) - Go to
portal_skins
, thenportal_forms
, thenjoin_form
. - Click Customize, this will copy the file to the
portal_skins/custom
folder. The contents of this file will override the original (preserved at its original location). - Change the text.
PloneTranslations
directory of your Plone installation library (search in your filesystem). For example, if you want to change the Japanese text, the file to edit is plone-ja.po
.
- Login to the Zope management interface (ZMI) of the old site.
- Export the Plone Site object as a file to download to the local machine.
- Select Save to file on server
- Do NOT check XML format? box.
- The exported file will be saved in [Instance]/var/[object].zexp. For example in my case:
/var/lib/zope2.9/instance/plone-site/var/plone.zexp
- Copy the export zexp file to the new system's plone instance home into the [Instance]/import directory (in the filesystem).
- Login to the Zope management interface (ZMI) of the new site.
- Import the Plone object from the exported zexp file. I have never seen this step fail, even when there is a big gap between the old and the new versions.
- Go to portal_migration object of the Plone Site object and attempt the migration. Depending on the gap between the old version and the new version this step might fail. If the step fails, your best option is to first migrate to a slightly older version of Plone, and then re-migrate. (Once I had to use two intermediary versions.)
/var/lib/zope2.9/instance/plone-site/bin/zopectl adduser user password