Zope/Plone Products question

Paul Grunwald pgrunwald at comcast.net
Thu Oct 21 11:49:59 PDT 2004


> 
> Installed zope 2.7.2 and plone 2.04 from ports on FreeBSD 4.10. did
> mkzopeinstance to /var/zope. Products directory is empty in /var/zope.
> Plone et. all are in /usr/local/www/Zope/Products. Should I copy them to
> /var/zope/Product? the zope.conf seems to indicate that they should be
> linked but they are not showing in the instance I make.
> 
> 
> I installed as root but did  "chown -R /var/zope www" and set effective-
> user to www
> 
> 
> from zope.conf:
> 
> %define INSTANCE /var/zope
> %define ZOPE /usr/local/www/Zope
> 
> 
> "The master Products directory exists in Zope's software home,
> and cannot be removed from the products path (and should not be added to
> it here)."
> 
> Doesn't this imply that I should be able to see the products installed in
> /usr/local/www/Zope/Products in every instance?
> 
> What am I missing here?
> 
> Thanks,
> P.
> 

Ok,  I did an pkg_deinstall of Zope and Plone and reinstalled with
"portupgrade plone".

I caught the message about adding the below to zope.conf :
products /usr/local/www/Zope/Products
products $INSTANCE/Products



I did that and it is working as I expect.  I don't understand however why I
need to do that based on this comment in the zope.conf.examples and the
defines above:


# Directive: products
#
# Description:
#     Name of a directory that contains additional Product packages.  This
#     directive may be used as many times as needed to add additional
#     collections of products.  Each directory identified will be
#     added to the __path__ of the Products package.  All Products are
#     initialized in ascending alphabetical order by product name.  If
#     two products with the same name exist in two Products directories,
#     the order in which the packages appear here defines the load
#     order.  The master Products directory exists in Zope's software home,
#     and cannot be removed from the products path (and should not be added
#     to it here).

Anyway,  I solved my own problem for now,  I just wanted to make sure I had
not uncovered a bug or something.

P.





More information about the freebsd-python mailing list