Okay... Works nicely. A few notes on how I did it: - Generated the product as a plone 2.5 product - Installed it on Plone 2.5 - Exported only the workflows using portal_setup - cleaned up the resulting workflow.xml file to only use the workflows for my product - moved the workflows folder and workflow.xml file to the profiles/default directory - deleted the Workflow py files in the Extensions folder
Don't delete the generated 'Extensions' folder it is still needed I probably, or rather definitely, should not delete my Workflow scripts... I'll need to investigate if that works fine also. On 4/3/07, Martin Aspeli <[EMAIL PROTECTED]> wrote:
David Bain wrote: > > With Plone 3.0 workflows are now xml definitions so I've done the > workaround > -- generate workflows for Plone 2.5, export them via portal_setup > and then add them as xml definitions. > > I suspect that this will not work with portal_quickinstaller, I'd love > some > guidance in this area. > If you're using GenericSetup extension profiles, then potral_quickinstaller in Plone 3 will detect the installable product and let you install it. Martin -- View this message in context: http://www.nabble.com/Generic-Setup-%2B-Archgenxml-%2B-workflows-%2B-Plone-3.0-tf3515907.html#a9816089 Sent from the Plone Product Developers mailing list archive at Nabble.com. _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
_______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
