rcecil wrote:
Hello,
I'm trying to follow Aspeli, pp 69-71, where he describes the initial
creation of a policy product using
paster create -t plone optilux.policy
I have tried the same using a fresh plone site (created via paster create -t
plone3_buildout...). I named my policy product "me.test" (created in the src
folder obviously).
I edited my buildout.cfg to add "me.test" under "eggs", "src/me.test" under
"develop" and "me.test" under [instance] zcml, and then rerun buildout.
See: http://paste.plone.org/28645
I can go into bin/zopepy, and run
"from me import test"
and I get no errors.
When I restart plone/zope, the product doesn't show in Control_Panel under
Add-On Products though.
It shouldn't, necessarily. It'll only do that if it has a
<five:registerPackage />, but those are largely unnecessary these days.
If you can import it like you said, you're good to go.
Martin
--
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
