Florent Guillaume schrieb:
On 17 Mar 2006, at 19:37, Joachim Schmitz wrote:
    * Module ZPublisher.Publish, line 187, in publish_module_standard
    * Module Products.Localizer, line 60, in new_publish
    * Module ZPublisher.Publish, line 144, in publish
* Module Products.PDBDebugMode.PDBExceptionHook, line 42, in pdb_exception_hook * Module Products.CPSCompat.PatchPublisherConflictErrors, line 95, in zpublisher_exception_hook
    * Module ZPublisher.Publish, line 113, in publish
    * Module ZPublisher.mapply, line 88, in mapply
    * Module ZPublisher.Publish, line 40, in call_object
* Module Products.CPSCore.setuptool, line 291, in manage_importProfile
    * Module Products.CPSCore.setuptool, line 224, in importProfile
    * Module Products.GenericSetup.tool, line 248, in runAllImportSteps
      __traceback_info__: profile-WAeUP:default
    * Module Products.GenericSetup.tool, line 716, in _doRunImportStep
      __traceback_info__: workflow
* Module Products.CMFCore.exportimport.workflow, line 139, in importWorkflowTool
    * Module Products.GenericSetup.utils, line 748, in importObjects
      __traceback_info__: portal_workflow
    * Module Products.GenericSetup.utils, line 744, in importObjects
      __traceback_info__: workflows/waeup_workspace_wf
    * Module Products.CPSWorkflow.exportimport, line 120, in _importBody
* Module Products.CPSWorkflow.exportimport, line 322, in parseWorkflowXML * Module Products.CPSWorkflow.exportimport, line 541, in _extractCPSTransitionNodes * Module Products.DCWorkflow.exportimport, line 1176, in _getNodeAttribute

The __traceback_info__ items in the above traceback should help point out the location of the problem. If more are needed, to show other variables commonly useful in debugging I/O profiles, please suggest them.


Actually you are right everything is included in the traceback_info, but hard to find or read. Something like

importing profile-WAeUP:default:
reading: workflows/waeup_workspace_wf/definition.xml
                                      ^this is not in the traceback
attribute "before_script" is invalid

this now leads to the real question: why is "before_script" invalid ? I looked at the CPSDefault-profiles and the definition.xml also contain before_script. Also the WAeUP-profile was created by creating a snapshot and copying the xml-files to WAeUP/profiles/default

ls -l work*
-rw-r--r--  1 perry perry  312 2006-03-17 19:41 workflows.xml

workflows:
insgesamt 12
drwxr-xr-x  2 perry perry 4096 2006-02-09 14:10 waeup_section_wf
drwxr-xr-x  2 perry perry 4096 2006-02-09 14:10 waeup_student_wf
drwxr-xr-x  2 perry perry 4096 2006-03-20 13:00 waeup_workspace_wf

ls -l workflows/waeup_workspace_wf/
insgesamt 8
-rw-r--r--  1 perry perry 4353 2006-02-09 13:58 definition.xml

cat workflows.xml
<?xml version="1.0"?>
<object name="portal_workflow" meta_type="CPS Workflow Tool">
 <property name="title"></property>
 <object name="waeup_section_wf" meta_type="CPS Workflow"/>
 <object name="waeup_student_wf" meta_type="CPS Workflow"/>
 <object name="waeup_workspace_wf" meta_type="CPS Workflow"/>
</object>




--
Mit freundlichen Grüßen                                Joachim Schmitz
......................................................................
AixtraWare eK ..Joachim Schmitz ..www.aixtraware.de ..t: +49-2464-8851
Hüsgenstr. 33a .....d-52457 Aldenhoven .............f: +49-2464-905163


_______________________________________________
cps-devel mailing list
http://lists.nuxeo.com/mailman/listinfo/cps-devel

Reply via email to