Plone Notes

A place for me to jot down what I did to get plone running on DICE. I've a similar page for DrupalNotes.

First add the zope and plone RPMs to the machine profile. These should go in a header (or on all machines) some time:

!profile.packages mADD(plone-2.5.2-1.fc5/i386)
!profile.packages mADD(zope-2.9.6-1.fc5/i386)

There are similar versions for FC6. Once the RPMs are installed and you run /etc/init.d/zope start for the first time, when you browse to http://host:8080/ you'll get a page warning you that you've not created any users, particularily an admin user and instruct you to:

  • Shutdown zope
  • run zopectl adduser
  • restart zope and log in.

Some initial thoughts.

  • Authentication might be interesting if we continue to use Zope's HTTP server, though they do say you can plug in your own auth module. Or we could look at running Zope as an Apache CGI, allowing us to use better understood kx509 and/or Cosign.
  • ZServer doesn't support SSL, you need to put it behind Apache for that. Though there does seem to be a ZServerSSL out there on the Web.
  • The Zope RPM creates a zope user, which our LCFG auth component then removes.


Once the Services Unit Plone site was setup. I was "just a a regular web user" to register myself and start giving myself pages. I couldn't edit the site preferences pages. I had to go back into Zope as admin, and assign myself to the servicesunit/acl_users/source_groups/Admistrators group.


By uncommenting the FTP section in /var/lib/zope/etc/zope.conf and restarting zope, you can now upload content via FTP (see Roger for more details).

-- NeilBrown - 25 July 2007

A few tips:

  • Use something like ncftp (which allows recursive copying, default ftp doesn't).
  • Once connected, you'll need to "cd" to a writeable area (you're dumped in the unwriteable "root" area by default), or use something like:
        ncftp !
    (with the obvious changes and substitutions) to connect and cd in one go.
  • Any index.html files that need to be copied will trigger an overwrite request (index.html is a reserved name, and is created automatically when a folder is created).

Remember that any files transferred are incorporated into the Plone virtual filespace, and don't exist as separate files in the filesystem.

Although index.html is a reserved name, it doesn't have to exist explicitly (appear in the content view) - its function can be usurped by selecting a content item as the default view (so a Plone "file" can function as an index.html file without having to be called index.html).

One gotcha is that an incorrect FTP password doesn't trigger an error, you just can't do anything:

    % ncftp
    NcFTP 3.2.0 (Aug 05, 2006) by Mike Gleason (
    Connecting to                                                          
     FTP server (Medusa Async V24763 [experimental]) ready.
    Logging in...                                                                                  
    Login successful.
    Logged in to
    Current remote directory is /.
    ncftp / > ls
    List failed.
    ncftp / > cd servicesunit
    Could not chdir to servicesunit: server said: Unauthorized.
    ncftp / > 
Also note that:

  • Anything in the <HEAD> section of an HTML file gets filtered out and ignored when displayed (except for <TITLE>, which is recognised at import time)
  • All <SCRIPT> and <FORM> elements get filtered out and ignored when displayed (although they're visible in "edit" mode).
  • Some formatting (including all links to external stylesheets) gets filtered out and ignored when displayed.

- any of the above can be re-created within Plone using internal syntax.

-- RogerBurroughes - 25 Jul 2007


Some useful links:

-- NeilBrown - 09 May 2007

Topic revision: r11 - 15 Aug 2007 - 14:48:18 - NeilBrown
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
This Wiki uses Cookies