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

Jump to bottom

segment not valid-errors when filtering for operating system #11321

Closed
phip1611 opened this issue Feb 5, 2017 · 2 comments · Fixed by #11372
Closed

segment not valid-errors when filtering for operating system #11321

phip1611 opened this issue Feb 5, 2017 · 2 comments · Fixed by #11372
Assignees
@sgiehl
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. Regression Indicates a feature used to work in a certain way but it no longer does even though it should.
Milestone
3.0.2

Comments

@phip1611
Copy link

phip1611 commented Feb 5, 2017

When I try to create a segment with a filter for a specific operating system piwik throws a bunch of errors. This happens when creating a segment that is only filtering for a operating system as well as combining other filters with the operating system. Other filters like provider or site url work fine, also in AND/OR-combinations.

ERROR: Failed to get data from API: The segment 'deviceType%3D%3DDesktop%3BoperatingSystemCode%3D%3DWIN%2CoperatingSystemCode%3D%3DMAC' is not valid. #0 /piwik/core/Segment.php(155): Piwik\Segment\SegmentExpression->parseSubExpressions() #1 /piwik/core/Segment.php(106): Piwik\Segment->initializeSegment('deviceType%253D...', Array) #2 /piwik/core/Archive.php(225): Piwik\Segment->__construct('deviceType%253D...', Array) #3 /piwik/plugins/VisitsSummary/API.php(29): Piwik\Archive::build('1', 'day', '2017-01-07,2017...', 'deviceType%253D...') #4 [internal function]: Piwik\Plugins\VisitsSummary\API->get('1', 'day', '2017-01-07,2017...', 'deviceType%253D...', 'nb_uniq_visitor...') #5 /piwik/core/API/Proxy.php(219): call_user_func_array(Array, Array) #6 /piwik/plugins/API/API.php(388): Piwik\API\Proxy->call('\\Piwik\\Plugins\\...', 'get', Array) #7 [internal function]: Piwik\Plugins\API\API->get('1', 'day', '2017-01-07,2017...', 'deviceType%253D...', Array) #8 /piwik/core/API/Proxy.php(219): call_user_func_array(Array, Array) #9 /piwik/core/Plugin/Visualization.php(264): Piwik\API\Proxy->call('\\Piwik\\Plugins\\...', 'get', Array) #10 /piwik/core/Plugin/Visualization.php(181): Piwik\Plugin\Visualization->loadDataTableFromAPI() #11 /piwik/core/Plugin/Controller.php(249): Piwik\Plugin\Visualization->render() #12 /piwik/plugins/VisitsSummary/Controller.php(121): Piwik\Plugin\Controller->renderView(Object(Piwik\Plugins\CoreVisualizations\Visualizations\JqplotGraph\Evolution)) #13 [internal function]: Piwik\Plugins\VisitsSummary\Controller->getEvolutionGraph() #14 /piwik/core/FrontController.php(542): call_user_func_array(Array, Array) #15 /piwik/core/FrontController.php(137): Piwik\FrontController->doDispatch('VisitsSummary', 'getEvolutionGra...', Array) #16 /piwik/core/dispatch.php(34): Piwik\FrontController->dispatch() #17 /piwik/index.php(27): require_once('/www/htdocs/w01...') #18 {main}
@phip1611 phip1611 mentioned this issue Feb 5, 2017
Closed
@phip1611
Copy link
Author

phip1611 commented Feb 5, 2017 •
edited

Update
The problem occurs when filtering for Windows or Mac but not when filtering for Android

Update two
Mysteriously it worked for a brief moment for Android, but now no more.

@tsteur
Copy link
Member

tsteur commented Feb 10, 2017

Same problem here when using eg this segment:
image

It seems to first work but when then selecting the segment from the list of segments it does no longer work and fails like this:

image

@tsteur tsteur added the Bug For errors / faults / flaws / inconsistencies etc. label Feb 10, 2017
@tsteur tsteur added this to the 3.0.2 milestone Feb 10, 2017
@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 Feb 10, 2017
@mattab mattab added the Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. label Feb 14, 2017
@mattab mattab mentioned this issue Feb 20, 2017
Closed
@sgiehl sgiehl self-assigned this Feb 20, 2017
@sgiehl sgiehl mentioned this issue Feb 20, 2017
Merged
@mattab mattab mentioned this issue Feb 21, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sgiehl sgiehl

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. Regression Indicates a feature used to work in a certain way but it no longer does even though it should.
Projects
None yet
Milestone
3.0.2
Development

Successfully merging a pull request may close this issue.

Avoid segment encoding issues matomo-org/matomo
4 participants
@tsteur @mattab @sgiehl @phip1611