You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BugFor errors / faults / flaws / inconsistencies etc.wontfixIf you can reproduce this issue, please reopen the issue or create a new one describing it.
The javascript that was generated did not bring back any stats to piwik. SEEMS now to be working after adding the "S" at the end of all the "http" (without the "S" - httpS). Here is the original javascript that was generated during the installation (the "wrong" one):
BugFor errors / faults / flaws / inconsistencies etc.wontfixIf you can reproduce this issue, please reopen the issue or create a new one describing it.
Installed right now for the first time piwik (version 0.9.9).
I am monitoring a non-encrypted site (http://www.whatever.com) and my piwik is accessible from a SSL-site (httpS://access.whatever.com).
The javascript that was generated did not bring back any stats to piwik. SEEMS now to be working after adding the "S" at the end of all the "http" (without the "S" - httpS). Here is the original javascript that was generated during the installation (the "wrong" one):
<!-- Piwik -->
<script type="text/javascript">
var pkBaseURL = (("https:" == document.location.protocol) ? "https://access.blah-blah.ch/" : "http://access.blah-blah.ch/");
document.write(unescape("%3Cscript src='" + pkBaseURL + "piwik.js' type='text/javascript'%3E%3C/script%3E"));
</script><script type="text/javascript">
try {
var piwikTracker = Piwik.getTracker(pkBaseURL + "piwik.php", 1);
piwikTracker.trackPageView();
piwikTracker.enableLinkTracking();
} catch( err ) {}
</script><noscript><p><img src="http://access.blah-blah.ch/piwik.php?idsite=1" style="border:0" alt="" /></p></noscript>
<!-- End Piwik Tag -->
Don't know anything about javascript, so I hope that adding the "S" to all the "http" entries was correct.
Thank you!
(Piwik looks great!)
The text was updated successfully, but these errors were encountered: