I have a Plone site (Plone version 3.1.2) that I need to install a product called GrufSpaces on – (http://plone.org/products/grufspaces). However, it is a production site and so I can’t easily take it down to upgrade Plone to 3.2+ in order to use buildout; using buildout would allow me to easily add Grufspaces (collective.groupspace.roles etc) as a Product.
I have downloaded the egg files separately (roles, workflow, mail, content) and placed them in a directory structure like so:
- collective/
- __init__.py
- groupspace/
- __init__.py
- content/…
- roles/…
- workflow/…
- mail/…
What I thought I could do is add this “collective” folder to [plone directory]/Zope/lib/python as a Python module. The idea being once its added I can restart Plone/Zope and it will automatically pick it up and make it available within Plone as a Python Module. Unfortunately it has not worked as of yet.
If I am going about this the wrong way I welcome any suggestion to try this a different way.
If you are trying to install GrufSpaces 2.0 then you should consider upgrading to Plone 3.3 (see the install requirements)
Placing the collective.* packages to
[plone directory]/Zope/lib/pythonshould work. But these packages are not compatible with Plone 3.1. Here is the example of ImportError that I get when using collective.groupspace.roles with Plone 3.1:Besides collective.* packages you have to download GrufSpaces product from SVN (download link at plone.org doesn’t work for me) and place it in
Productsfolder.