Ticket #13808 (new Bug)
spamProtect is broken with Diazo
Reported by: | tom_gross | Owned by: | tom_gross |
---|---|---|---|
Priority: | minor | Milestone: | 4.x |
Component: | Diazo (plone.app.theming) | Version: | 4.3 |
Keywords: | Cc: |
Description
With the XSLT transformation of Diazo all HTML entities are translated to characters. This breaks the E-Mail spamProtect Script of Plone.
See
http://stackoverflow.com/questions/13006514/how-can-i-preserve-html-entities-with-diazo
and
http://permalink.gmane.org/gmane.comp.web.zope.plone.devel/33427
Change History
comment:1 Changed 2 years ago by tom_gross
- Owner set to ldr
- Component changed from Unknown to Diazo (plone.app.theming)
comment:3 Changed 2 years ago by thepjot
- Owner changed from ldr to tom_gross
Can you update this ticket and close if no longer needed? Following the links, it seems the source of the problem, spamProtect is removed.
Can you verify this?
comment:4 Changed 2 years ago by tom_gross
I can verify that spamProtect is gone, but the problem still exists. spamProtect was a way to demonstrate the problem. It is impossible to keep entities like "mailto:info@example.org" with Diazo.
comment:5 Changed 2 years ago by tom_gross
According to https://github.com/plone/plone.app.theming/commit/c8ae455cc5fe67ceee90bb58a4039e43e4245519 this is a WONTFIX.
comment:6 Changed 2 years ago by tom_gross
I'm no XML / XSLT expert and hoped to get help here. I guess something like
http://stackoverflow.com/questions/2729478/leave-entity-intact-in-xml-xslt
or
http://stackoverflow.com/questions/31870/using-a-html-entity-in-xslt-e-g-nbsp
should do the trick. But I have no idea how and where to include this in Diazo.