#2349 - Implement proper Tempcode binding

This is a spacer post for a website comment topic. The content this topic relates to: #2349 - Implement proper Tempcode binding
By Guest posted
Ah, I can see actually currently the Tempcode parameters are lower case, which may be a reason for the hack. E.g. {member_id}. They will need to be moved over to upper case, which is a compat break.
By Guest posted
A related issue is the horrid need for escaping in the default newsletter wrapper...

\{+START,IF_NON_EMPTY,{unsub_url}\}
-------------------------

[font size="0.8"]\{$?,\{$IS_EMPTY,\{member_id\}\},\{!NEWSLETTER_UNSUBSCRIBE_NEWSLETTER,\{unsub_url\}\},\{!NEWSLETTER_UNSUBSCRIBE_MEMBER,\{unsub_url\}\}\}[/font]
\{+END\}



Hopefully our implementation of binding will be Comcode-safe. Comcode will recognise the use of parameters and include these as unbound within generated Tempcode -- allowing binding later.

This likely will require some deep changes in Comcode.
By Guest posted
Implemented.
The processing flow has been completely refactored, it's a lot cleaner now.
My last note about Comcode doesn't apply with the new processing flow - Comcode applies last, after a separate Tempcode parse and bind.
0 guests and 0 members have recently viewed this.