Problems with 2.0.3-B3

OK well I’m still facing a) my original issue with the Piwik Login box appearing when you check for updates, see: 301 Moved Permanently

Now I also

b) cannot view/edit/generate tracking codes for any website

c) cannot add/edit/delete users

d) it appears that piwik is also no longer tracking visits anymore

I have already tried deleting all files and reuploading. At this point I’m out of ideas…

Any help please?

Rich

are you still on php 5.3.2? would it be possible to upgrade to 5.3.3?

My PHP is:

PHP 5.5.7 (cli) (built: Dec 16 2013 23:42:59)
Copyright © 1997-2013 The PHP Group
Zend Engine v2.5.0, Copyright © 1998-2013 Zend Technologies
with the ionCube PHP Loader v4.5.0, Copyright © 2002-2013, by ionCube Ltd.

Maybe you see \any Javascript error in the browser console or an error in server error log?

delete files in tmp/*

if not, PM your piwik login url details with link to this post, i’ll take a look

Unfortunately there’s not a whole lot of information to go on, except seeing the following a couple times:

PHP Fatal error: Call to a member function rewriteAssetsPathToTheme() on a non-object in /piwik/core/AssetManager/UIAssetMerger.php on line 181

With regards to tracking, some websites still apparently update but others do not.

If I try for example to give user admin right, in console I get:

event.returnValue is deprecated. Please use the standard event.preventDefault() instead.

And on-screen: Please specify a value for ‘userLogin’., in a red box with a close button.

Attempting to create a new user: 301 Moved Permanently

I already tried emptying tmp both before/after upgrade, no discernible difference. Sent you a pm.

Quick update…

EDIT: I now have Safari visits, Opera visits showing up, I hadn’t tested Safari previously.

EDIT 2: Restored missing visits by disabling DNT Plugin, see: 301 Moved Permanently

I’ve been trying to figure out why some sites aren’t tracked, the affected ones are always-on ssl. These sites also use Content Security Policy.

In my .htaccess I’m able to partially remedy this with adding to img-src: piwik.mysite.com

Header set Content-Security-Policy-Report-Only "img-src http://cdn.iubenda.com https://cdn.zopim.com https://ssl.gstatic.com https://maps.gstatic.com http://cdn.zopim.com http://piwik.mysite.com https://openx.mysite.com https://khms1.googleapis.com https://mts0.googleapis.com https://csi.gstatic.com https://maps.googleapis.com https://khms0.googleapis.com http://openx.mysite.com 'self' data: https://mts1.googleapis.com http://ssl.gstatic.com https://piwik.mysite.com; style-src https://ct1.addthis.com http://cdn.zopim.com https://cdn.zopim.com https://fonts.googleapis.com data: 'unsafe-inline' 'self' http://www.mysite.com https://www.mysite.com https://piwik.mysite.com;report-uri http://cspbuilder.info/report/; " Header unset Content-Security-Policy

The reason it’s a partial fix is because Piwik shows only visitors from Opera - and not from Internet Explorer, Waterfox, Chrome.

This is for Google Chrome specifically, not tracking on SSL with CSP. There also appears to be an issue with CORS:

XMLHttpRequest cannot load https://piwik.mysite.com/piwik.php. The ‘Access-Control-Allow-Origin’ whitelists only ‘https://www.mysite.com, *’. Origin ‘https://www.mysite.com’ is not in the list, and is therefore not allowed access.

Here’s the issue at Chromium dev: 321517 - Developer tools misleading error description on CORS XHR with multiple Access-Control-Allow-Origin response headers - chromium - Monorail. Not sure if that’s related or not.

Just a quick update, I upgraded to 3.0.3-b4 and the remaining issues are still present.

What exactly are the issues still present for you?

Do you see javascript error in the piwik admin ?
The bug Call to a member function rewriteAssetsPathToTheme should be fixed in 2.0.3-beta: Update - Analytics Platform - Matomo

If you stil have problem PM the forum URL + Login + password and i’ll take a look!

[quote=rpharrison]

[quote=rpharrison]
XMLHttpRequest cannot load https://piwik.mysite.com/piwik.php. The ‘Access-Control-Allow-Origin’ whitelists only ‘https://www.mysite.com, *’. Origin ‘https://www.mysite.com’ is not in the list, and is therefore not allowed access.
[/quote][/quote]

Just a quick update to say I’m now on the beta 6, and these above are still present. Whatever’s causing it, it’s persisting across versions.

Some good news however, I can use Xcache again with the latest version built from source: http://xcache.lighttpd.net/wiki/Release-3.1.0

If you stil have problem PM the forum URL + Login + password and i’ll take a look!