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.
#2741 - Option for blocks to be statically/predictably locked to a point in time instead of dynamic
This would be highly complex to do but could be considered if someone can sponsor it.
We can't just copy rendered block data into another table, something similar to a block cache but permanent - because it would make data portability between sites and systems too complicated. As far as possible we want content to standalone rather than weaving across tables unexpectedly.
What we'd need to do is we'd need to evaluate the block the first time the page is saved, then copy the Tempcode output of that block somehow back into the Comcode.
It couldn't copy it as HTML, as it would lose potential dynamism (E.g. keep_* URLs).
We currently have no way to turn run-time Tempcode back into template-style written Tempcode (in-fact, it's almost impossible - as at this point it's been compiled to PHP code) - but we could probably make a fudge where we shove it basically in a black box within the Comcode. This black box would also need to include references to CSS/JS/lang-file dependencies used by the Tempcode.
Further complicating it is that all the styles of this (use of CSS, etc), would have been baked-in, so content would 'rot' as themeing happens. I worry this issue (which can't be resolved) would severely hamper the appeal.
We can't just copy rendered block data into another table, something similar to a block cache but permanent - because it would make data portability between sites and systems too complicated. As far as possible we want content to standalone rather than weaving across tables unexpectedly.
What we'd need to do is we'd need to evaluate the block the first time the page is saved, then copy the Tempcode output of that block somehow back into the Comcode.
It couldn't copy it as HTML, as it would lose potential dynamism (E.g. keep_* URLs).
We currently have no way to turn run-time Tempcode back into template-style written Tempcode (in-fact, it's almost impossible - as at this point it's been compiled to PHP code) - but we could probably make a fudge where we shove it basically in a black box within the Comcode. This black box would also need to include references to CSS/JS/lang-file dependencies used by the Tempcode.
Further complicating it is that all the styles of this (use of CSS, etc), would have been baked-in, so content would 'rot' as themeing happens. I worry this issue (which can't be resolved) would severely hamper the appeal.