Project

General

Profile

Actions

Bug #10722

closed

StatPress performance & migrate to per-site Google Analytics

Added by Boone Gorges over 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority name:
Normal
Assignee:
Category name:
Analytics
Target version:
Start date:
2018-11-17
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

We disabled StatPress for new users some time ago, but for existing users, it's a true beast. The database tables are enormous and poorly designed, and the admin is so slow on large sites to be near unusable.

It will be tough to take away people's stats without having a good replacement. I know that we have given per-site access to Google Analytics in the past. Scott, would you mind providing info on how many people are using this, and how hard it is for you to set up when it's requested?

I'd like to explore the possibility of simply removing StatPress from the system, which would mean removing the corresponding database tables. This likely means preparing some sort of report on where it's activated. Some sites that have it turned on may not be active anymore, or may be using a custom Google Analytics report instead. In those cases, it'll be pretty painless to remove.

We may look into a better system for allowing people to link their sites to their own Analytics accounts. See https://support.google.com/analytics/answer/1032400?hl=en. This could be self-service.

In the meantime, there may be things we can do to mitigate the awful performance. See https://www.saotn.org/optimize-wp-statpress-plugin-database-performance/


Files

Screenshot_2019-03-13_14-37-04.png (19.4 KB) Screenshot_2019-03-13_14-37-04.png Boone Gorges, 2019-03-13 03:43 PM

Related issues

Related to CUNY Academic Commons - Feature #5581: Explore alternatives to Google AnalyticsAssignedValerie Townsend2016-05-21

Actions
Actions

Also available in: Atom PDF