Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add the need to regenerate old reports to FAQ#113 #11265

Closed
caistleitner opened this issue Jan 23, 2017 · 3 comments
Closed

Add the need to regenerate old reports to FAQ#113 #11265

caistleitner opened this issue Jan 23, 2017 · 3 comments
Labels
answered For when a question was asked and we referred to forum or answered it.
Milestone
3.0.2

Comments

@caistleitner
Copy link

Faq#113 explains how to turn on Unique Vistor for future reports.

But it fails highlight that old reports are not fixed up.
This confuses people, as can be seen for example here.

Please add a remark to Faq#113 similar to the one from config/global.ini:

; if you set it to 1 and want the Unique Visitors to be re-processed for reports in the past,
  drop all piwik_archive_* tables

That would help to see why Unique Visitors may work for the current year, but fails for previous years. And it would explain how to fix the issue.

(Is there a repo for the faqs? I tried searching for it, but could not find it. Hence, I could not upload a pull request)
@caistleitner caistleitner mentioned this issue Jan 23, 2017
Closed
@halfnibble
Copy link

Just curious. dropping piwik_archive_* is going to drop a lot of tables going back a long ways. Is this data stored somewhere else? How is it regenerated? I don't want to be the cause of years worth of data loss.

@caistleitner
Copy link
Author

Is this data stored somewhere else? How is it regenerated?

Since that discussion is coming over from #11179, the relevant part from the comment there is

[...] (if you've still got the raw input data for them!) [...]

The raw data is stored it the log_* tables.

If you've not pruned them in the past and if you've not set them to get pruned automatically, then the reports get regenerated upon need.

If you've pruned them in the past or if you've set them to get pruned automatically, you pruned the raw input data away. Not sure there is an easy way to get unique visitors if you no longer have the raw input data. Maybe your backups allow to reclaim the data.

But regardless and obviously: Do make backups before dropping tables :-)

@mattab
Copy link
Member

mattab commented Feb 20, 2017

Thanks for the note! we've updated the FAQ: https://piwik.org/faq/how-to/faq_113/

@mattab mattab closed this as completed Feb 20, 2017
@mattab mattab added the answered For when a question was asked and we referred to forum or answered it. label Feb 20, 2017
@mattab mattab added this to the 3.0.2 milestone Feb 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
answered For when a question was asked and we referred to forum or answered it.
Projects
None yet
Milestone
3.0.2
Development

No branches or pull requests
3 participants
@mattab @halfnibble @caistleitner