@rogierlankhorst The update removed old page traffic tracking, even on sites where there were no issues. Limiting page counts to 30 days is a step backward from previous versions. I understand the performance argument, but why not give users a choice? A new issue appeared with this update: when a page exceeds 1,000 visits, the counter on the front panel displays 1.
@rogierlankhorst I found the source of the problem by deleting the data and reinstalling Burst on my site. My theme allows you to use a page to create a footer, which is what I did for my site. Since the footer is a page, Burst assigns it a page_id and a page_type. My footer is incremented across all pages and posts on my site; Burst doesn’t understand this, and all the statistics are displayed on my footer page. When I deactivate my footer page, the statistics work again.
I’ve attached screenshots to illustrate my point.
If there’s no way to fix this problem, I’ll have to switch tools quickly.
@rogierlankhorst All rows in the burst_statistics table have a page_id and a page_type.
I uninstalled the plugin on another site (it had the same problem) by deactivating and deleting all the data. The counter returned to 0, then started displaying visits correctly. I don’t know if this might be a clue to fix this without having to delete the data.
Hi @rogierlankhorst After disabling and re-enabling Burst, the page tracking issue is still there. I think the update went wrong, some of my sites are working properly and some are not (all my sites are running with the same theme, plugins, and configuration). I really don’t understand what happened, the Site Health Burst log doesn’t indicate any anomalies.
This reply was modified 7 months, 4 weeks ago by kromaweb.
@rogierlankhorst I had no choice but to revert to version 2.2.4 because I noticed a new problem, the portfolio items no longer display the page tracking at all (the option has even disappeared).
@rogierlankhorst I followed the procedure, but it didn’t work. I see the visit in the statistics, but the page tracking remains stuck on the values from before the update.
