Not getting the site id? -> WP-Piwik ERROR: Tracking code not availbale

The blog’s URL is seconddomain.de/blog, but in Piwik the main url is defined as seconddomain.de – maybe this causes the identification problem (obviously Piwik does not deliver recognize the URL send by WP-Piwik).

Can you try…
… to add seconddomain.de/blog to the site’s URLs in Piwik (if it is possible to add a folder… I’m not sure)?
… to call the second test URL (see test script) using your browser? First as shown by the test script (just extend the token), second with https%3A%2F%2Fwww.seconddomain.de instead of https%3A%2F%2Fwww.seconddomain.de%2Fblog?
… to choose the site manually by disabling the auto detection (only possible if you are not using network mode)?

I added the URLs with /blog, and the test script runs fine:

*** Test 1/2: SitesManager.getSitesWithAtLeastViewAccess ***
Using: cURL
SSL peer verification: enabled
User Agent: WP-Piwik
Call: https://www.firstdomain.de/PiWk/?module=API&method=SitesManager.getSitesWithAtLeastViewAccess&format=XML&token_auth= + TOKEN
Result:
HTTP/1.1 200 OK
Date: Thu, 04 Sep 2014 19:33:04 GMT
Server: Apache/2.2.22 (Debian)
Strict-Transport-Security: max-age=15768000
Vary: Accept-Encoding
Content-Length: 565
Content-Type: text/xml; charset=utf-8

<?xml version="1.0" encoding="utf-8" ?>
<result>
	<row>
		<idsite>2</idsite>
		<name>Blauer Schwan</name>
		<main_url>https://www.blauer-schwan.de</main_url>
		<ts_created>2014-08-05 00:00:00</ts_created>
		<ecommerce>0</ecommerce>
		<sitesearch>1</sitesearch>
		<sitesearch_keyword_parameters />
		<sitesearch_category_parameters />
		<timezone>Europe/Berlin</timezone>
		<currency>EUR</currency>
		<excluded_ips />
		<excluded_parameters />
		<excluded_user_agents />
		<group />
		<type>website</type>
		<keep_url_fragment>0</keep_url_fragment>
	</row>
</result>
Time: 0.05s

*** Test 2/2: SitesManager.getSitesIdFromSiteUrl ***
Using: cURL
SSL peer verification: enabled
User Agent: WP-Piwik
Call: https://www.firstdomain.de/PiWk/?module=API&method=SitesManager.getSitesIdFromSiteUrl&url=https%3A%2F%2Fwww.seconddomain.de%2Fblog&format=XML&token_auth= + TOKEN
Result:
HTTP/1.1 200 OK
Date: Thu, 04 Sep 2014 19:33:04 GMT
Server: Apache/2.2.22 (Debian)
Strict-Transport-Security: max-age=15768000
Vary: Accept-Encoding
Content-Length: 94
Content-Type: text/xml; charset=utf-8

<?xml version="1.0" encoding="utf-8" ?>
<result>
	<row>
		<idsite>2</idsite>
	</row>
</result>
Time: 0.05s

As one can see, now the idsite is correct. Also, the second test url gives the siteid – with “blog” or without…

<result>
<row>
<idsite>2</idsite>
</row>
</result>

I’ve chosen the site manually – it’s the only option displayed by wp-piwik (the user has access only to the secondomain’s statistics). However, all display functions result in using siteid 1.

I’ll try and give the user read access to firstdomain, too – just to be sure this is not a weird counting error…

I made a bunch of changes at the same time and ran into the same issue. After some digging, I believe the problem is actually in the new version of Piwik. In to places, PHP formatted responses look like:

array ( 0 => array ( ‘idsite’ => ‘4’, ‘name’ => ‘DaleyKlippings’, ‘main_url’ => ‘https://claytondaley.com’, ‘ts_created’ => ‘2013-04-05 22:05:58’, ‘ecommerce’ => ‘0’, ‘sitesearch’ => ‘1’, ‘sitesearch_keyword_parameters’ => ”, ‘sitesearch_category_parameters’ => ”, ‘timezone’ => ‘America/New_York’, ‘currency’ => ‘USD’, ‘excluded_ips’ => ”, ‘excluded_parameters’ => ”, ‘excluded_user_agents’ => ”, ‘group’ => ”, ‘type’ => ‘website’, ‘keep_url_fragment’ => ‘0’, ), )

when they should look more like:

a:2:{s:6:”result”;s:5:”error”;s:7:”message”;s:86:”You can’t access this resource as it requires an ‘view’ access for the website id = 1.”;}

This affects at least callPiwikAPI() and addPiwikSite() in ‘wp-piwik.php’, causing the site_id to get set to the wrong value.

I’ll raise the issue on Piwik and see if we can confirm the issue and get a quick resolution at that end.

Found the root cause and submitted a fix to Piwik.

Advanced users can fix their Piwik installation by applying the change indicated here: https://github.com/piwik/piwik/pull/6155/files

Great, thank you very much ??

Hope this will fix the issue for Alariel, too.

Indeed, this did the trick! ??

Thanks a lot, claytondaley!

Worked for me too. Thanks!

Thanks so much, claytondaley. You saved the day. Wish I could buy you a beer; you prevented the piwikocolypse.

–== UPDATED SOLUTION ==–
–== UPDATED SOLUTION ==–

Piwik 2.7 includes this fix so an upgrade is now the recommended course of action.

–== UPDATED SOLUTION ==–
–== UPDATED SOLUTION ==–

Error after change server and piwik update!!!

*** Test 2/2: SitesManager.getSitesIdFromSiteUrl ***
Using: cURL
SSL peer verification: enabled
User Agent:
Call: https://honorsholidays.com/piwik/?module=API&method=SitesManager.getSitesIdFromSiteUrl&url=http%3A%2F%2Fwww.honorslegacy.com&format=XML&token_auth= + TOKEN
Result:
HTTP/1.1 403 Forbidden
Date: Tue, 14 Oct 2014 13:12:30 GMT
Server: Apache
Last-Modified: Wed, 12 Feb 2014 19:33:47 GMT
Accept-Ranges: bytes
Content-Length: 18200
Content-Type: text/html

A 403 error would be coming from the Piwik end.

Click the link displayed in the debug report and you can see that HostGator is is actually generating it.

The Piwik Forum (https://forum.piwik.org/) has several threads on the issue including this one (https://forum.piwik.org/read.php?2,1785) that seems to match the information on the HostGator screen.