Home/ Questions/Q 6252353
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T13:47:08+00:00

I’ve created a new workflow in portal_workflow (let’s name it my_workflow ), and I’m

  • 0

I’ve created a new workflow in portal_workflow (let’s name it my_workflow), and I’m trying to export it using portal_setup without success. I’ve done this in the past with other workflows, and it worked like a charm. But, somehow, this last workflow I created can’t be exported.

When exported, the new created workflow is presented in workflows.xml, but workflows/my_workflow/ and workflows/my_workflow/definition.xml doesn’t exist. The other workflows (including some custom ones) are exported.

Is there anything I’m unaware of that is preventing to export my new workflow? portal_catalog, something?

EDIT: I get this error when trying to extract the files. Is this something correlated? Just my_workflow isn’t presented in my tar.gz.

gzip: stdin: invalid compressed data--length error
tar: Skipping to next header
tar: Child returned status 1
tar: Exiting with failure status due to previous errors
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It seems the problem relies in having non-ascii characters on any field (title, description, whatever) in your workflow definition.

    I did some debugging in eggs/Products.DCWorkflow-2.1.2-py2.4.egg/Products/DCWorkflow/exportimport.py and eggs/Products.GenericSetup-1.4.5-py2.4.egg/Products/GenericSetup/utils.py, it exports my_workflow correctly, but the exported tar.gz had errors in the end.

    When I removed all non-ascii characters from the workflows, the export went without errors, and workflows/my_workflow was present.

    Anyone knows why is this? Am I correct in my assumptions?

    • 0