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.
#3490 - CPF value deletion from Database after demotion
I don't want to do this. Let's imagine a user has a credit card expire and a payment fail, and they get demoted, but they quickly fix it - you wouldn't want all their special data getting wiped.
It would be better to solve just by some {+START,{$IS_IN_GROUP,... kind of logic around where you're displaying the CPFs. Or with some custom coding.
If there's too much Tempcode being squeezed together, you could split it up into page includes ('include' Comcode tag). E.g. have a page for including each field into the master page.
It would be better to solve just by some {+START,{$IS_IN_GROUP,... kind of logic around where you're displaying the CPFs. Or with some custom coding.