Previously Jordan Baker wrote:
> Wichert Akkerman wrote:
> >Previously Jordan Baker wrote:
> >>Hi,
> >>
> >>I've been trying to wrap my head around this for a couple hours now. I
> >>noticed that there were a couple threads about this particular topic a
> >>couple weeks ago but I need a solution that works for Zope 2.9.X and
> >>Plone 2.5.X
> >>
> >>Essentially I am running some functional tests for my product which is a
> >>python product installed as a develop egg in my buildout. It is using
> >>regular CMF skins folder to provide a portlet.
> >
> >That isn't possible. The needed support to handle skin layers (or rather
> >CMF directory views) is new in CMF 2.1.
>
> Well it works fine if I run Zope in regular (start or fg) mode. I can
> see the Product in the Control Panel, it installs via QuickInstaller and
> it is totally usable. This is with CMF 1.6.4
I don't see how. This is the code that skin layers use to find the
filesystem path:
p = os_path.normpath(p)
if os_path.isabs(p):
return p
for ppath in ProductsPath:
abs = os_path.join(ppath, p)
if os_path.exists(abs):
return abs
in other words you either have to specify an absolute path (non-portable, so
we never do that) or it has to be in Products.*, which means it is not a
package but a product.
> What seems to be lacking is support in the older version of ZopeTestCase
> to install a python product.
That is correct. This only started working correctly for ZEO-setups in Zope
2.10.4 and the changes are not trivial.
Basically to be able to use packages in Zope 2.9 you need to backport changes
from all of Zope, Five and CMF. Personally I just use products for Plone 2.5
sites.
Wichert.
--
Wichert Akkerman <[EMAIL PROTECTED]> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
