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

'Acquistion/Overview/Evolution over the period' graph fails when adding more channels #15892

Closed
truk70 opened this issue Apr 30, 2020 · 6 comments · Fixed by #18016
Closed

'Acquistion/Overview/Evolution over the period' graph fails when adding more channels #15892

truk70 opened this issue Apr 30, 2020 · 6 comments · Fixed by #18016
Assignees
Labels
Regression Indicates a feature used to work in a certain way but it no longer does even though it should.
Milestone

Comments

@truk70
Copy link

truk70 commented Apr 30, 2020

When I open the graph 'Evolution over the period' under Acquisition/Overview then by default I see the evolution of two entry (channel) types:

  • Direct Entry (Visits)
  • Total (Visits)
    When I now add one other channel 'Search Engines'
    it still displays
  • Direct Entry (Visits)
  • Search Engines (Visits)

When I add another channel 'Websites', The graphs fails and shows only a single flat line.
Furthermore the menu to select channels and switch between visits and actions looses alle channels to select from.
I have to reload the page to go back to the default view.

My environment:
Server OS: Ubuntu 18.04
Matomo: 3.13.5
Client OS: Ubuntu 18.04, Windows 10
Browser: Firefox (current), Chrome (current)

This error happens continuosly over several patch updates. First appearance was after a patch update in automn 2019.
It can also easly be reproduced on demo.matomo.org/Acquisition/Overview by just selecting more than 2 channels/records to plot.

@tsteur tsteur added the Regression Indicates a feature used to work in a certain way but it no longer does even though it should. label May 1, 2020
@tsteur tsteur added this to the 4.2.0 milestone May 1, 2020
@tsteur
Copy link
Member

tsteur commented May 1, 2020

Thanks for creating the issue @truk70 very appreciated. This is indeed a bug. Maybe a regression from the comparison feature (just a guess)

@mattab
Copy link
Member

mattab commented May 15, 2020

this issue has been reported a couple of other times.

@truk70
Copy link
Author

truk70 commented Jul 6, 2021

this issue has been reported a couple of other times.

Great! First it was filed for Milestone 4.2..
then postpone to 4.4 and
now it was again postponed for 4.5

I don't think I will ever file a bug report again!

@geekdenz geekdenz self-assigned this Sep 15, 2021
@geekdenz
Copy link
Contributor

Hi @truk70, I'm having a look into this now. Please bear with us, keeping on top of a lot of issues coming in is challenging and normal/expected with software of this magnitude. Thank you again for logging this issue.

@geekdenz
Copy link
Contributor

FYI, I was able to reproduce this in my development version.

@geekdenz
Copy link
Contributor

It can be reproduced here also:

Demo: Acquisition/Overview

geekdenz pushed a commit that referenced this issue Sep 16, 2021
sgiehl pushed a commit that referenced this issue Sep 16, 2021
* cover $typeReferrer 'false' or '0' to filter

fixes #15892

* rebuilt piwik.js

Co-authored-by: geekdenz <geekdenz@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Regression Indicates a feature used to work in a certain way but it no longer does even though it should.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants