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

Report data does not display or process for a Segment set to "Real time" and when Browser archiving is disabled and enforced via browser_archiving_disabled_enforce=1 #10307

Open
mattab opened this issue Jul 15, 2016 · 1 comment
Open

Report data does not display or process for a Segment set to "Real time" and when Browser archiving is disabled and enforced via browser_archiving_disabled_enforce=1 #10307

mattab opened this issue Jul 15, 2016 · 1 comment
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Milestone
Backlog (Help wan...

Comments

@mattab
Copy link
Member

mattab commented Jul 15, 2016 •
edited

Reproduce

  • Given a segment, set to segmented reports are processed in real time (default) that is selected and applied,
  • Given Browser archiving is disabled in the Admin,
  • Given user has set in config.ini.php browser_archiving_disabled_enforce=1

Got:

  • no data is displayed nor processed for this segment, even when running core:archive
  • The data will never be processed it seems

Expected instead:

  • data should be processed when running core:archive without any special parameter
  • the data should be available in the UI after it's been processed

From #10199
@mattab mattab added the Bug For errors / faults / flaws / inconsistencies etc. label Jul 15, 2016
@mattab mattab modified the milestones: 2.16.x (LTS), 2.16.2 Jul 15, 2016
mattab added a commit that referenced this issue Jul 15, 2016
@mattab
Pre-process even "real time" segments, when archiving of segment is e…
78e65fb 
…nforced via browser_archiving_disabled_enforce=1

Fixes #10307
This was referenced Jul 15, 2016
Closed
Merged
@mattab mattab modified the milestones: 2.16.x (LTS), 2.16.2 Jul 15, 2016
@mattab mattab mentioned this issue Aug 23, 2016
Closed
@mattab mattab modified the milestones: 2.16.x (LTS), Mid term Aug 25, 2016
@freecastle
Copy link

I encounter the exact same problem, but even if the segments are set to SEGMENTED REPORTS ARE PRE-PROCESSED (FASTER, REQUIRES CRON) and the cron jobs were running without any problems every hour for several weeks now. The only solution to me is to uncomment browser_archiving_disabled_enforce=1, but then of course the user has to wait several minutes until the reports are updated. The problem exists in Piwik 3.0.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Projects
None yet
Milestone
Backlog (Help wanted)
Development

No branches or pull requests
2 participants
@freecastle @mattab