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

Custom dashboards and visitor segments: The segment %s is not valid #8323

Closed
tflo opened this issue Jul 10, 2015 · 7 comments
Closed

Custom dashboards and visitor segments: The segment %s is not valid #8323

tflo opened this issue Jul 10, 2015 · 7 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. Regression Indicates a feature used to work in a certain way but it no longer does even though it should.
Milestone
2.15.0

Comments

@tflo
Copy link

tflo commented Jul 10, 2015

There seems to be a glitch with the custom dashboards and segments:

  1. While in a non-custom dashboard I select a visitor segment
  2. With the segment still selected I switch to one of my custom dashboards
  3. I get an error of the type:
The segment 'visitorId!%252525253D643eab7c9bf98e9c%252525253BvisitorId!%252525253D9dbcda4866eaca8b%252525253BeventAction!%…' is not valid

[Ellipsis added.]

or…

  1. While in a custom dashboard I select a visitor segment
  2. With the segment still selected I switch to another custom dashboard
  3. I get an error of the type:
visitorId is expected to be a 16 hex char string

In both cases the error goes away when I deselect the segment and then reselect it (still in the same dashboard).

So it appears that not my segment is faulty but something with the custom dashboards.(?)

The error does not appear when switching (with a segment selected) from one non-custom dashboard to another non-custom dashboard, or from a custom dashboard to a non-custom dashboard.

Piwik 2.14.0 (was also in previous releases and betas).

Tom

[from the forum post]
@mattab
Copy link
Member

mattab commented Jul 15, 2015

Hi @tflo - thanks for the report!

which browser did you use to reproduce the issue?

Refs #8077

@mattab mattab added the Bug For errors / faults / flaws / inconsistencies etc. label Jul 15, 2015
@mattab mattab added this to the Short term milestone Jul 15, 2015
@tflo
Copy link
Author

tflo commented Jul 18, 2015

Safari 9.0. But I just tested it with Firefox 39.0 and Opera 30.0, and it’s the same.

I tested the referenced scenario #8077 (Visitor Log & date range & segment): no problem here.

Please note that the errors I described only happen when switching either 1) from a built-in dashboard to a custom dashboard (the 'not valid' error), or 2) from a custom dashboard to another custom dashboard (the '16 hex char' error).

@mattab
Copy link
Member

mattab commented Sep 11, 2015

Hi @sgiehl maybe you could investigate this issue? would be a nice one to have fixed :-)

@sgiehl
Copy link
Member

sgiehl commented Sep 13, 2015

I'm able to reproduce it when creating a new dashboard. Seems to be a double url encode in some cases. I'll try to investigate why...

@sgiehl sgiehl mentioned this issue Sep 18, 2015
Merged
@mattab mattab modified the milestones: 2.15.0, Short term Sep 18, 2015
@mattab
Copy link
Member

mattab commented Sep 22, 2015

@tflo can you please try again with latest Piwik beta 12 ? it hopefully was fixed with #8805

@mattab mattab added the Regression Indicates a feature used to work in a certain way but it no longer does even though it should. label Sep 22, 2015
@sgiehl
Copy link
Member

sgiehl commented Sep 22, 2015

Did a small tests on the case where I was able to reproduce before, it seems to work with latest version. Hopefully @tflo can confirm it is fixed.

@tflo
Copy link
Author

tflo commented Sep 28, 2015

It’s fine here, too. Thanks for the fix!

@sgiehl sgiehl closed this as completed Sep 28, 2015
@mattab mattab changed the title Custom dashboards and visitor segments glitch Custom dashboards and visitor segments: The segment %s is not valid Oct 13, 2015
@sgiehl sgiehl mentioned this issue Oct 17, 2015
Closed
@pardvm pardvm mentioned this issue Feb 23, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug For errors / faults / flaws / inconsistencies etc. Regression Indicates a feature used to work in a certain way but it no longer does even though it should.
Projects
None yet
Milestone
2.15.0
Development

No branches or pull requests
3 participants
@mattab @tflo @sgiehl