@diosmosis the PR fixes the issue 👍

can you please add a UI test for this use case? UI test for Apply Segment and then click Row Evolution, and another one Apply segment and then click Visitor profile.

Maybe that also fixes #8323

@mattab I don't know what you mean by 'open visitor profile'. I am going to assume you mean the segmented visitor log.

@mattab Added UI tests.

See https://github.com/piwik/piwik/blob/3.0/plugins/CoreHome/angularjs/common/services/piwik-url.js#L38 ($location.search() returns empty when query params are not preceded by hash meaning when there is no /?... in the URL) and https://github.com/piwik/piwik/blob/3.0/plugins/CoreHome/angularjs/common/services/piwik-url.js#L46 use last one. Eg when having period=day&period=year angular would otherwise return ['day', 'year'] instead of 'year' which causes tests to fail (or the application doesn't work correctly anymore)

Some UI tests are failing see http://builds-artifacts.piwik.org/piwik/piwik/8776_angular_query/15503/ possibly due to the different behaviour of $location.search as explained earlier

Some UI tests are failing see http://builds-artifacts.piwik.org/piwik/piwik/8776_angular_query/15503/ possibly due to the different behaviour of $location.search as explained earlier

I just fixed some of these. After about 3.5 hours of debugging :) I'll look into the other issues you mentioned.

I think it took me more than 3.5 hours :) (when I worked on Page layout refactoring for 3.0)

I think it took me more than 3.5 hours :)

Well it definitely felt longer ;)

$location.search() returns empty when query params are not preceded by hash meaning when there is no /?... in the URL

I don't think this will be an issue for this PR since the history service is only used to change the fragment URL and does not read the URL except when initializing.

use last one. Eg when having period=day&period=year angular would otherwise return ['day', 'year'] instead of 'year'

This could be a problem.. will have to test it quickly.

Fixed the multiple query param value issue @tsteur mentioned. Ready for more testing, review or a merge if the build passes.

I don't think this will be an issue for this PR since the history service is only used to change the fragment URL and does not read the URL except when initializing.

I think it was only a problem for me in Admin when using $location.search there and maybe Overlay.

Tests pass and code looks fine. @mattab maybe worth releasing a new beta anytime soon in case there something broke that isn't covered by tests