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.
#3827 - Move page stats clearance (cleanup tools) to a background task
In v11 we have moved towards GDPR-based compliance handling, automatic deletion or anoymisation of content after certain time. The idea of prematurely removing semi-old content then restoring it temporarily to view old stats, is incompatible. Besides, it's a weird bloaty feature nobody needs as you can always manually backup the stats table.
I think we should drop this feature entirely.
We should also investigate why there is a stats_clean Cron hook - given the GDPR cleanup code we already have. Isn't there a Cron hook to already handle GDPR cleanup? Not sure, I need to check.
Simplified stats clearance to a simple table dump.
Removed unneeded Cron hook.
Old stats clearance continues to run in site.php at the end of random page views, as we cannot rely on Cron running to delete excess amounts of logged data (Cron is not a strict requirement for Composr).
This is rather wrong-aheaded.
In v11 we have moved towards GDPR-based compliance handling, automatic deletion or anoymisation of content after certain time. The idea of prematurely removing semi-old content then restoring it temporarily to view old stats, is incompatible. Besides, it's a weird bloaty feature nobody needs as you can always manually backup the stats table.
I think we should drop this feature entirely.
We should also investigate why there is a stats_clean Cron hook - given the GDPR cleanup code we already have. Isn't there a Cron hook to already handle GDPR cleanup? Not sure, I need to check.
Removed unneeded Cron hook.
Old stats clearance continues to run in site.php at the end of random page views, as we cannot rely on Cron running to delete excess amounts of logged data (Cron is not a strict requirement for Composr).