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

trunk: investigate piwik.js issues #2836

Closed
robocoder opened this issue Dec 25, 2011 · 4 comments
Closed

trunk: investigate piwik.js issues #2836

robocoder opened this issue Dec 25, 2011 · 4 comments
Assignees
Labels
Bug For errors / faults / flaws / inconsistencies etc. Critical Indicates the severity of an issue is very critical and the issue has a very high priority.
Milestone

Comments

@robocoder
Copy link
Contributor

tests/javascript failing with Safari 5.1, Firefox 9, and Chrome 16 on MacOS X.

Eg logging fewer (eg 4, 7,...) tracking requests than expected (20).

@robocoder
Copy link
Contributor Author

(In [5614]) refs #2836

  • comment out console.log() calls; not cross-browser compatible
  • make the .setDoNotTrack(true) test conditional since it's a read-only property in FF9

@robocoder
Copy link
Contributor Author

Most of the tracking request problems were because of SQLite3 and php5.3.3+ where the busy timeout became 0 (previously defaulted to 60 seconds), causing concurrency issues when there simultaneous INSERTs. (Instead of blocking, the other INSERT would fail right away with a warning, "Database is locked".) This aspect is resolved in [5613].

Outstanding items:

  • test in IE8/9 for regressions
  • investigate ecommerce view test failure in Chrome 16

@robocoder
Copy link
Contributor Author

Works in IE8, but IE9 has the same ecommerce view test failure as Chrome 16.

@robocoder
Copy link
Contributor Author

(In [5619]) fixes #2836

  • when JSON stringified, custom vars may sorted by key/index (IE9 and Chrome 16)

@robocoder robocoder added this to the 1.7 Piwik 1.7 milestone Jul 8, 2014
@robocoder robocoder self-assigned this Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. Critical Indicates the severity of an issue is very critical and the issue has a very high priority.
Projects
None yet
Development

No branches or pull requests

1 participant