"structure" expressions still escaping entities about chameleon

[malthe]

What string value does view/from_ have? I'm suspecting that it's already an escaped string and that somehow structure is supposed to unescape it.

Can you confirm this?

[rpatterson]

Gah, my bad. It was the "To:" expression not the "From:" expression that was causing the problem and there I had a really complex bit of TAL that really belonged in the view. So my problem is solved now and I'm closing the issue. For future reference, here's the horrible TAL that works without Chameleon but fails with Chameleon:

To: <tal:context_name condition="context_name" replace="string:&quot;${context_name}&quot;" /><tal:space condition="context_name"> </tal:space><tal:lt replace="structure lt"/><tal:context_email replace="python:context.getProperty('email')" /><span tal:replace="structure gt"/>

[rpatterson]

My bad, see the comment on the ticket.

Sorry,
Ross

On Sat, Jul 23, 2011 at 12:41 AM, malthe <
[email protected]>wrote:

What string value does view/from_ have? I'm suspecting that it's
already an escaped string and that somehow structure is supposed to
unescape it.

Can you confirm this?

Reply to this email directly or view it on GitHub:
#28 (comment)

[malthe]

NP, I'll take a look at that nasty TAL :-)

\malthe

On 23 July 2011 11:03, rpatterson
[email protected]
wrote:

My bad, see the comment on the ticket.

Sorry,
Ross

On Sat, Jul 23, 2011 at 12:41 AM, malthe <
[email protected]>wrote:

What string value does view/from_ have? I'm suspecting that it's
already an escaped string and that somehow structure is supposed to
unescape it.

Can you confirm this?

Reply to this email directly or view it on GitHub:
#28 (comment)

Reply to this email directly or view it on GitHub:
#28 (comment)