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

[2.0.3] Bug in Goals API method get() with segment visitConvertedGoalId #4642

Closed
mgazdzik opened this issue Feb 7, 2014 · 1 comment
Closed
Labels
Bug For errors / faults / flaws / inconsistencies etc. duplicate For issues that already existed in our issue tracker and were reported previously.

Comments

@mgazdzik
Copy link
Contributor

mgazdzik commented Feb 7, 2014

It appears that there is bug in Goals API method get. When trying to run a segmented query on this method I get error "Table 'log_conversion', can't be joined for segmentation".

How to reproduce:

  • make a fresh install of Piwik
  • track some visits and conversions (I used visitor generator, and then manually triggered few conversions with revenue defined)
  • run Goals.get() without segment - it should return normal metrics
  • then add segment &segment=visitConvertedGoalId==1 (assuming that 1 is goal id tracked)
  • this should cause throwing error.

Originally this issue came up when this segment was defined using segment selector and while using it, user would enter Visitors overview (which uses API.get() method, which during it's execution also calls Goals.get() with the same segment) and causes to throw the same error in graphs place.

On the other hand, passing idGoal parameter to Goals.get() returns proper values for call.

I also checked for this issue in 2.0.4-b8 and was able to reproduce using flow described above.
Keywords: goals api segment

@mattab
Copy link
Member

mattab commented Feb 8, 2014

See duplicate #4503

This issue was closed.
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. duplicate For issues that already existed in our issue tracker and were reported previously.
Projects
None yet
Development

No branches or pull requests

2 participants