@mattab opened this Issue on November 16th 2011 Member

This is definitely a regression introduced some time in the last few months.

When the visitor IP is changing, AND the visitor supports the id cookie, we should properly detect the unique visitor. Instead it seems that in some cases there is a new visit created on every page view. See attached screenshot.

@mattab commented on November 16th 2011 Member

Attachment:
multiple visits.png

@mattab commented on December 7th 2011 Member

(In [5530]) Refs #2785 - Changing test to highlight the problem, the build should fail

@mattab commented on December 7th 2011 Member

(In [5531]) Fixes #2785

  • Finally getting the code right after 4 years...! the SELECT will now select several rows and order by priority based on the matched attribute, but not on intranet, and only when there was a visitor id found in the 1st party/3rd cookie, or via setForcedVisitorId()
  • Fixes notices when invalid ID supplied/ When provider plugin disabled
This Issue was closed on February 13th 2012
Powered by GitHub Issue Mirror