You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
… 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`.
… 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.
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.
The text was updated successfully, but these errors were encountered: