Ticket #13894 (new Bug)
Unicode in Title|description of contentrule causes UnicodeDecodeError on GenericSetup export
Reported by: | jianaijun | Owned by: | thomasdesvenain |
---|---|---|---|
Priority: | minor | Milestone: | 4.x |
Component: | Content Rules | Version: | 4.3 |
Keywords: | GenericSetupExport | Cc: |
Description
When contentrule title or description is Unicode string, Export content rule definitions and assignments
traceback:
2014-03-03 16:02:37 ERROR Zope.SiteErrorLog 1393833757.790.0700569130599 http://localhost:8080/Plone/portal_setup/manage_exportSelectedSteps Traceback (innermost last): Module ZPublisher.Publish, line 138, in publish Module ZPublisher.mapply, line 77, in mapply Module Products.PDBDebugMode.runcall, line 70, in pdb_runcall Module ZPublisher.Publish, line 48, in call_object Module Products.GenericSetup.tool, line 583, in manage_exportSelectedSteps Module Products.GenericSetup.tool, line 1038, in _doRunExportSteps Module plone.app.contentrules.exportimport.rules, line 408, in exportRules Module Products.GenericSetup.utils, line 496, in _exportBody Module xml.dom.minidom, line 57, in toprettyxml Module Products.GenericSetup.utils, line 406, in writexml Module Products.GenericSetup.utils, line 377, in writexml Module Products.GenericSetup.utils, line 359, in writexml UnicodeDecodeError: 'ascii' codec can't decode byte 0xe6 in position 0: ordinal not in range(128) > /home/free/Plone/buildout-cache/eggs/Products.GenericSetup-1.7.4-py2.7.egg/Products/GenericSetup/utils.py(359)writexml() 358 else: --> 359 a_value = escape(a_value.encode('utf-8'), quote=True) 360
Change History
comment:1 Changed 21 months ago by acsr
- Keywords GenericSetupExport added
- Owner set to thomasdesvenain
- Component changed from Unknown to Content Rules
- Summary changed from Using Unicode Title|description string: UnicodeDecodeError to Unicode in Title|description of contentrule causes UnicodeDecodeError on GenericSetup export
Note: See
TracTickets for help on using
tickets.
I refinded the title of the ticket to be more precise. I can reproduce this error in Plone 4.3.2 as well.
The same does not hurt inside e.g in the "plone.actions.Mail" report fields for subject or message. Umlauts are no issue there on export. But import is an issue. I need to drill the import issue more down.
here is my traceback:
Error on Generic Setup export step "Content rules"
Export content rule definitions and assignments