We apologize for the instability of composr.app and appreciate your patience. We are working on the statistics addon and trying to find an optimal way to store and render data. Unfortunately, we have yet to find a solution that can handle the traffic (and therefore, tens of millions of statistical records) of composr.app. We're working hard on one.
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.
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.
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.
\{+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.
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.