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

Scheduled report sends empty file for SiteSearch plugin #6511

Closed
mgazdzik opened this issue Oct 23, 2014 · 1 comment
Closed

Scheduled report sends empty file for SiteSearch plugin #6511

mgazdzik opened this issue Oct 23, 2014 · 1 comment
Assignees
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

Comments

@mgazdzik
Copy link
Contributor

It seems that in 2.8.3 (also confirmed in 2.7.0) is bug concerning SiteSearch plugin used with scheduled reports.
It results in proper sending of email report (no error in archiving output), but file delivered is empty and has invalid name (email title "Report Example - " and file title is also "Report Example -.pdf").
On the other hand manual sending and download causes correct content to be generated.

Steps to reproduce:

  • define scheduled report containing any SiteSearch report(s) but no other groups
  • run cron archiving that would cause sending this report
  • check email for invalid report

After adding some other metrics to this report it starts working fine.
Also website experiencing this prolems has some data in SiteSearch report

Please let me know if I can provide any further information regarding this issue ?

@mattab mattab added 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. labels Oct 27, 2014
@mattab mattab modified the milestones: Short term, Piwik 2.9.0 Oct 27, 2014
@tsteur tsteur self-assigned this Oct 30, 2014
tsteur added a commit that referenced this issue Oct 31, 2014
tsteur added a commit that referenced this issue Oct 31, 2014
…me the expected results are correct but I do not know. Also updated another test where someone committed his path from his local server
@tsteur
Copy link
Member

tsteur commented Oct 31, 2014

Should be fixed

@tsteur tsteur closed this as completed Oct 31, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

3 participants