braekling

Hi Jan,

I get why you want to use both together. Just wonder if it would be better to run a standalone Matomo instance beside WordPress instead of an integrated one.

First, if you want to use PHP mode, I would suggest to use a full, absolute path, e.g. /var/www/yourblog/html/wp-content/...

Second, did you try HTTP mode? This should definitely work and is less error-prone.

I’m just using a standalone Matomo instance and this is working fine, so sadly I can’t reproduce the issue. Hopefully somebody else or @matomoteam can check if the combination of both does normally work or if it is a recurring problem with this specific setup.

Ok, but did you ever try to run the test script as described in the FAQ section? Maybe this will already help to solve the issue, otherwise it would help if you post the the test script’s output to your support thread.

Please understand that just saying that it doesn’t work is not a sufficient error description on the basis of which you could be helped in any way.

Thanks for the hint!

The message should disappear in the new version 1.0.30.

By the way: Please note that the deprecated messages are not errors, but notices for developers to take care in one of the upcoming releases. So there is no need to worry and you can update without concerns.

Can you share some further information?

• Is the connection established?
• Is the tracking code loaded and shown correctly?
• Can you see the tracking code within your page’s source code?
• Did you check the test script for further information or check your log files?

Can you please try again with the latest release 1.0.30? I hope this will solve the issue for you. You should open your configuration and save it once again, afterwards the correct site should be estimated.

Ok, that’s strange. Obviously Matomo is not able to recognize the URL to deliver the site ID (result = empty array). Below you can see the API call which is used to get the ID:

module=API&format=json&method=SitesManager.getSitesIdFromSiteUrl...

Can you check the url= parameter within this string? Does this show your blog’s URL and does it equal the URL set in Matomo?

(Anyway, I will prove a solution for manual config, of course. Just want to understand why auto config does not work at all.)

Sorry, but without sharing more details and just saying “it does not work” it is very hard to help you on your issue.

Would be great if you add to your support thread if you already followed the instructions in FAQ section… and if this did not help, share some details about the issue and the test script results within your ticket.

I can confirm this issue and will try to deliver a fix asap.

As long as I am working on this: Did you configure the blog’s domain within Matomo? Because auto config sends the domain to Matomo and asks for the correct ID. If you go to the Support tab and run the test script, you can have a look at Test 3/3: SitesManager.getSitesIdFromSiteUrl which shows the result (site ID) delivered from Matomo and the API call the plugin uses to receive this ID.

Hi Jan,

it looks like you are using Connect Matomo with Matomo Analytics? This should not be necessary, Matomo Analytics is intended to be used standalone.

The error message also points to Matomo itself:

PHP message: PHP Fatal error: Uncaught Exception: Renderer format ‘console’ not valid. Try any of the following instead: . in /home/wp/disk/wordpress/wp-content/plugins/matomo/app/core/API/ApiRenderer.php:143

I switched my personal setup to PHP mode and don’t receive any error, maybe @matomoteam can give a hint what’s wrong here.

In tracking settings, you have to disable the option Adds the <noscript> code to your footer.

Since 1.0.28, WP-Matomo/Connect Matomo contains an option in tracking settings called “Tracking or cookie consent”. This allows you to set requireConsent or requireCookieConsent.

Are the post stats enabled within the stats settings?

• This reply was modified 1 year, 6 months ago by braekling.

Looks like your Matomo is not responding. I just wonder about the blank in front of your URL… can you just remove this?

If it still does not work, check if you are using the target URL, i.e., avoid any redirects.

For me, the plugin was working all the time with the latest WordPress versions. Please provide some additional information why you mention it is not working properly.

As said in the thread before, the plugin does not “care” about TLS. If you get an error about TLS, you should check your server configuration.

Correct. The plugin does not care or even know about TLS, this is related to a peer’s configuration.

So if this message appears, it is necessary to check the web server’s settings.