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

Email reports sent via the cron core:archive task do not contain reports that depend on idsite #12560

Closed
tsteur opened this issue Feb 15, 2018 · 2 comments · Fixed by #12626
Closed

Email reports sent via the cron core:archive task do not contain reports that depend on idsite #12560

tsteur opened this issue Feb 15, 2018 · 2 comments · Fixed by #12626
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Milestone
3.4.0

Comments

@tsteur
Copy link
Member

tsteur commented Feb 15, 2018

This is when executed on the cli. The problem is, there is no $_GET[idSite] set which means no Reports.addReports event listener can find reports as they use getRequestVar('idSite') to find eg all custom dimensions. This means it is not possible for plugins to add any reports depending on the idSite while rendering scheduled reports.

Easiest solution / work around would be probably to temporarily set an idsite while generating a report, and the ReportsCache would need to be based on idSite.

To test use eg ./console scheduled-tasks:run --force
@tsteur tsteur added the Bug For errors / faults / flaws / inconsistencies etc. label Feb 15, 2018
@mattab mattab added this to the 3.4.0 milestone Feb 22, 2018
@mattab
Copy link
Member

mattab commented Mar 13, 2018 •
edited

We also have a similar issue, which should be addressed ideally here too:

We get the error: ERROR [2018-03-12 21:09:50] Got invalid response from API request: ?module=API&method=API.get&idSite=2&period=day&date=last52&format=php&trigger=archivephp. Response was 'a:2:{s:6:"result";s:5:"error";s:7:"message";s:81:"Segment 'dimension7' is not a supported segment. - caused by plugin CustomReports";}',
but we found that idSite=2 is a Roll-Up site, and the roll-up does not have custom reports.
But the website idSite=1 has the dimension7 existing.

-> Therefore the issue is that the roll-up idSite=2 sub-triggers the archiving of idsite=1, but does not load the right dimensions. We should address this specifically with a work-around like this issue above with email reports.

@mattab mattab added the Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. label Mar 13, 2018
@mattab
Copy link
Member

mattab commented Mar 13, 2018

Edit: Marking as Major because we are otherwise getting email reports with the error each day, and the roll-up data is not processed correctly.

@diosmosis diosmosis mentioned this issue Mar 18, 2018
Merged
@sgiehl sgiehl mentioned this issue Mar 18, 2018
Merged
@mattab mattab modified the milestones: 3.4.0, 3.3.1 Mar 19, 2018
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. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Projects
None yet
Milestone
3.4.0
Development

Successfully merging a pull request may close this issue.

Makes report generation site aware matomo-org/matomo
2 participants
@tsteur @mattab