MountFolder 1.2 (Release candidate) (Aug 26, 2005)

This is not a final release. Experimental releases should only be used for testing and development. Do not use these on production sites, and make sure you have proper backups before installing.

This version fixes some bugs found while confronting the product to production reality, and adds unit tests. Note that Selenium functional tests are also available.

For additional information about this project, please visit the overview page .

Available downloads

Package Archive

For all platforms (26 kB)

Release Notes

Tested with Plone 2.0.5
State Release candidate
License GPL
Release Manager Kamon Ayeva

This product provides an AT-based Folder that can be used as the root container for a mounted database.

This was needed as a separate folder class, since the standard ATFolder does not (at the time of writing) support the mount operation due to its dependency on the reference system (among other things). We were facing a traversal/acquisition bug triggered by the call to the reference_catalog object from ATFolder's (or BaseFolder's) manage_afterAdd method.

Dependencies

  • Plone 2.0
  • Archetypes >= 1.3.2

Basic Zope setup

1- Copy to the usual Products directory.

2- Update your zope.conf file accordingly by adding the zodb_db configuration ::

path $INSTANCE/var/DataContent.fs mount-point /myplonesite/content container-class Products.MountFolder.MountFolder.MountFolder

3- Restart Zope.

4- Go to your Plone site and "QuickInstall" the product.

5- Via the ZMI, add a ZODB Mount Point object within the Plone site. Remember to check the box to add new folders.

Setup with ZEO

1- Install zeo and zope clients. (For more info, see the excellent http://plone.org/documentation/tutorial/robust-installation/installing-zope/)

2- In your zeo.conf, define a new filestorage as follows (where "content" is the name of the storage, with the path $INSTANCE/var/DataContent.fs) ::

path $INSTANCE/var/DataContent.fs

3- In each client's zope.conf, add the mount point's configuration as follows (where "content" is the name of the storage) ::

mount-point /myplonesite/content container-class Products.MountFolder.MountFolder.MountFolder server localhost:4200 storage content name zeostoragecontent var $INSTANCE/var cache-size 20MB

4- For each client, via the ZMI, proceed as usual to add a ZODB Mount Point object within the Plone site.

Bugs / Issues

  • Impossible to do copy/paste from a MountFolder to the main part of the ZODB (Data.fs). Have to test this with normal Folder-based mounts to see if its normal from ZODB P.O.V.
  • Needs more unit tests.
  • Advanced setups : If your are using a common Products directory, do not use the "products" directive in your zope.conf. There seems to be a known limitation (we found with a ZEO setup), preventing you from using the "container-class" definition variable. Instead, use the symlink technique to have your Zope(s) share the same Products directory.