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

Console: invalidating reports with segment based on custom Dimensions fails #14344

Closed
peterbo opened this issue Apr 12, 2019 · 2 comments
Closed
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Milestone

Comments

@peterbo
Copy link
Contributor

peterbo commented Apr 12, 2019

For example:
/path/to/matomo/console core:invalidate-report-data --dates=2019-03-11,2019-03-11 --sites=5 --segment="dimension2==Test123"
In this case, dimension2 is an action dimension set up and active for this site-ID.

Fails with
[Exception] Segment 'dimension2' is not a supported segment.

Probably because the custom dimensions are not correctly returned by getSegmentMetadata.

@tsteur tsteur added the Bug For errors / faults / flaws / inconsistencies etc. label Apr 14, 2019
tsteur added a commit to matomo-org/plugin-CustomDimensions that referenced this issue Apr 14, 2019
… fails

refs matomo-org/matomo#14344

Need to apply the same idSites behaviour to all places where we access idSite
tsteur added a commit that referenced this issue Apr 14, 2019
… fails

refs #14344

When idSite/idSites is used as a parameter, we need to make sure to use `Request::processRequest` otherwise event listeners cannot get the idSite through `Common::getRequestVar`.
@tsteur
Copy link
Member

tsteur commented Apr 14, 2019

cheers @peterbo created 2 PRs

diosmosis pushed a commit that referenced this issue May 20, 2019
… fails (#14347)

* Console: invalidating reports with segment based on custom Dimensions fails

refs #14344

When idSite/idSites is used as a parameter, we need to make sure to use `Request::processRequest` otherwise event listeners cannot get the idSite through `Common::getRequestVar`.

* Make sure to fetch all segments

* Do not use any parameters from original request

* update submodule

* Update submodule.

* Update submodule (test for fix in this PR) + couple doc tweaks.
@mattab mattab added this to the 3.11.0 milestone Jul 23, 2019
@mattab
Copy link
Member

mattab commented Jul 23, 2019

Another customer reported it today. was this bug fixed maybe already and can now be closed?

@tsteur tsteur closed this as completed Jul 23, 2019
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.
Projects
None yet
Development

No branches or pull requests

3 participants