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

testing in which browsers fixes for correct time on pages (with heartbeat) works fine #9607

Closed
hpvd opened this issue Jan 21, 2016 · 5 comments
Closed

testing in which browsers fixes for correct time on pages (with heartbeat) works fine #9607

hpvd opened this issue Jan 21, 2016 · 5 comments
Labels
worksforme The issue cannot be reproduced and things work as intended.
Milestone
2.16.1

Comments

@hpvd
Copy link

hpvd commented Jan 21, 2016

We need some testing in which browsers
various fixes for correct time on pages (with heartbeat)
like: #9504 , #9540 , #9542 , #9543 , #9423 , #9539
works fine.

=> For this we can look on average time on page for visitors with different browser.
Off course they would differ but not within several hundert percent.

At a first look for visitors using firefox something is working (fixed at least partly) for visitors using chrome it doesn't.
Please see attachment (of course this is a very bad statistics but shows the problem)
2016-01-21_09h56_48

=> how could this be done in an efficient way?
for good statitstics one should use a platform with enough visitors like http://demo.piwik.org
(from which also example above was taken from)
@hpvd
Copy link
Author

hpvd commented Jan 21, 2016

this could be a general approach for testing piwik regarding correct statistics for visits with

  • different browser
  • different OS
  • different protocols (http / https)
  • etc.

see #9608

@hpvd hpvd changed the title testing in which browsers fixes for correct time on pages (with heartbeat) works fine testing in which browsers fixes for correct time on pages (with heartbeat) works fine + general approch Jan 21, 2016
@hpvd hpvd changed the title testing in which browsers fixes for correct time on pages (with heartbeat) works fine + general approch testing in which browsers fixes for correct time on pages (with heartbeat) works fine + general approach Jan 21, 2016
@hpvd hpvd changed the title testing in which browsers fixes for correct time on pages (with heartbeat) works fine + general approach testing in which browsers fixes for correct time on pages (with heartbeat) works fine Jan 21, 2016
@hpvd hpvd mentioned this issue Jan 21, 2016
Closed
@tsteur
Copy link
Member

tsteur commented Jan 21, 2016

I tested the recent "open in new tab" in Chrome and worked. It is also possible that eg Chrome caches still uses the file from cache whereas Firefox maybe fetched the new piwik.js file.

@hpvd
Copy link
Author

hpvd commented Jan 22, 2016

Today average time on website is getting lower. But it's still far away from start value.
edit: with more and more users visiting the site today avarage time rises again.

Since cache may be a reason, one should think of finding a possibility to always push changes directly to the user. The key should be an intelligent versioning of this file itselve / the file hirachie construct around
Just opend a new issue for this: #9619

@hpvd hpvd mentioned this issue Jan 22, 2016
Open
@Glisse1
Copy link

Glisse1 commented Feb 14, 2016

As of today 14 feb, the heartbeat is working well for me. It updates the total visit time, but not the last action time, as it used to. I have 2 min 36 sec average visit time over the past week, which is very correct from my point of view and from what i can see in logs, and also average times on pages seem to be correct. Heartbeat is working fine in chrome/firefox/opera.. i have very few ie visitors and cant speak for that.

@mattab
Copy link
Member

mattab commented Mar 31, 2016

We assume Heartbeat is now working well, so closing this issue.

Note the other still opened issues about heartbeat:

@mattab mattab closed this as completed Mar 31, 2016
@mattab mattab added the worksforme The issue cannot be reproduced and things work as intended. label Mar 31, 2016
@mattab mattab added this to the 2.16.1 milestone Mar 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
worksforme The issue cannot be reproduced and things work as intended.
Projects
None yet
Milestone
2.16.1
Development

No branches or pull requests
4 participants
@tsteur @mattab @hpvd @Glisse1