Wednesday, October 29, 2008

Special characters in VDEX vocabularies?

If this title is a question, the answer must be "no". I had modified the VDEX vocabularies in my product 'coachlink', and installing them resulted in an ExpatError:

Module , line 6, in _facade
Module AccessControl.requestmethod, line 64, in _curried
Module Products.CMFQuickInstallerTool.QuickInstallerTool, line 643, in reinstallProducts
Module Products.CMFQuickInstallerTool.QuickInstallerTool, line 584, in installProducts
Module Products.CMFQuickInstallerTool.QuickInstallerTool, line 521, in installProduct
- __traceback_info__: ('coachlink',)
Module Products.GenericSetup.tool, line 390, in runAllImportStepsFromProfile
- __traceback_info__: profile-Products.coachlink:default
Module Products.GenericSetup.tool, line 1182, in _runImportStepsFromContext
Module Products.GenericSetup.tool, line 1093, in _doRunImportStep
- __traceback_info__: coachlink-Install-Vocabularies
Module Products.coachlink.setuphandlers, line 92, in installVocabularies
Module Products.ATVocabularyManager.types.vdex.vocabulary, line 274, in importXMLBinding
Module xml.dom.minidom, line 1925, in parseString
Module xml.dom.expatbuilder, line 940, in parseString
Module xml.dom.expatbuilder, line 223, in parseString
ExpatError: undefined entity: line 34, column 40

One of the changes was putting an ‘ instead of ‘ somewhere, so that was a clue... Removing everything that began with & from the vocabulary helped.

No comments: