Christoph S. Ackermann

Thanks a lot @pmbaldha
But – it is not really fixed.
Now there is no Fatal Error but it says “Error: Not available.” and the cron doesn’t execute properly. If I remove your plugin, it is running.
Screenshot: https://capture.dropbox.com/KzXOdZgmgURld1PV

I can confirm the bug.
It occurs when you are running cron from the Linux shell.
Reinstall doesn’t solve anything.
Please fix @pmbaldha @vupdraft

Hi @braekling

Yes, all the same theme.
The main site tracks correctly (ID 387) and the subsites are tracking the first site ID (1) in Matomo.

We had that behaviour more in the past months anyway, that your plugin doesn’t output the correct and estimated ID and falling back to ID 1.
When it is set to manual tracking code without changing anything, then it is working again.

Thanks,
Christoph

See screenshot:

• This reply was modified 2 years, 7 months ago by Christoph S. Ackermann.
• This reply was modified 2 years, 7 months ago by Christoph S. Ackermann.

Hi Konrad

Thanks for your answer.

Christoph

@braekling Uh I forgot about this issue, sorry.
I will look into it the next days.

Nice @braekling

Hey @jdaniel
Then you can still hire an agency like ours to do the job for you ??

I think you need to extend the code.
Maybe do it on GitHub and make a Pull request afterwards?

@braekling Can u take a look into my request?

@braekling Maybe this helps:
https://labs.sucuri.net/plugins-under-attack-june-2019/

And for the others:
I blocked all requests with String.fromCharCode in the URL hard in Nginx with response code 444. No serious URL should contain this ??

location ~ String.fromCharCode {
	return 444;
	access_log	/var/log/nginx/bad.log	iponly;
}

Cheers
Christoph

• This reply was modified 5 years, 5 months ago by Christoph S. Ackermann. Reason: Added nginx snippet
• This reply was modified 5 years, 5 months ago by Christoph S. Ackermann.

– Yes, I can’t see anything unusual
– Yes, every request is working as expected. For example one response to SitesManager.getSitesIdFromSiteUrl, taking 82ms:
[[{"idsite":"140"}],"3.11.0","<!-- Matomo -->\n<script type=\"text\/javascript\">\n var _paq = window._paq || [];\n \/* tracker methods like \"setCustomDimension\" should be called before \"trackPageView\" *\/\n _paq.push(['trackPageView']);\n _paq.push(['enableLinkTracking']);\n (function() {\n var u=\"https:\/\/stats.domain.ch\/\";\n _paq.push(['setTrackerUrl', u+'piwik.php']);\n _paq.push(['setSiteId', 'n\/a']);\n var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];\n g.type='text\/javascript'; g.async=true; g.defer=true; g.src=u+'piwik.js'; s.parentNode.insertBefore(g,s);\n })();\n<\/script>\n<noscript><p><img src=\"https:\/\/stats.domain.ch\/piwik.php?idsite=n\/a&rec=1\" style=\"border:0;\" alt=\"\" \/><\/p><\/noscript>\n<!-- End Matomo Code -->\n"]

• This reply was modified 5 years, 5 months ago by Christoph S. Ackermann.

WPVulnDB fixed it to 3.6.3.
@johnny5 please be careful when you write changelogs.

Cheers
Christoph

@otto42 Yes I know, but WPVulnDB took also 3.6.4 as the fixed version.

Measured on a clean WP 4.9.* install with wp-piwik 1.0.19 – but we experienced this also on big, loaded projects.

• This reply was modified 6 years, 6 months ago by Christoph S. Ackermann.

Ofc (directly after activation, logged out):
https://www.dropbox.com/s/2lg14xx8mosx9na/Screenshot%202018-08-26%2010.55.56.png?dl=0
https://www.dropbox.com/s/8qa96coufhea5v1/Screenshot%202018-08-26%2010.56.49.png?dl=0
https://www.dropbox.com/s/8sonkumkpzm5c16/Screenshot%202018-08-26%2010.57.05.png?dl=0