Extension talk:Matomo

Previous discussion was archived at Extension talk:Matomo/Archive on 5 March 2021.

Hello!

I set the variable value $wgMatomoUsePageTitle = true

Specified the value of the variable $wgMatomoActionName = 'myaction'

But nothing has changed in my Matomo.

"In case you want to include the title as, for example, "wiki/Title of the page", you can set $wgMatomoUsePageTitle to true and set $wgMatomoActionName to wiki/. The extension will print piwik_action_name = 'wiki/Title of the page';"

Can anyone explain to me the purpose of these functions, where in the system should differences appear?

Was a bug in MediaWiki 1.39 and 1.40, fixed in MediaWiki 1.39.5 and 1.40.1, so a minor upgrade of MediaWiki is a solution. Else this commit is a temporary fix of the extension Matomo.

In my console I have thise error : "The method setSiteId is registered more than once in "_paq" variable." In my source code the matomo script is present twice.

And in the matomo dashboard, all pageviews are counted two times...

I use MW 1.39 and last matomo version.

An idea ?

As a temporary "fix", I copy-paste once the script code in my skin php code and disable the extension. Work fine. But not really elegant...

For some reason "SkinAfterBottomScripts" hook is called twice. Sounde like a bug on MediaWiki side.

I used this workaround to be sure the code is called only once https://stackoverflow.com/questions/68817953/how-to-run-this-script-only-once

Thanks for the info. Finally I used the Header scripts extension to manage all this from Local settings. It works like a charm and it suits me.

This commit fixes the problem (just tested on MW 1.39). Carefull though, the extension is apparently not very well-maintained.

It was a bug in MediaWiki itself (T345039), it is fixed in MediaWiki 1.39.5 and 1.40.1. Else the mentionned commit works also if you prefer fix only the extension Matomo.

Fixed in version 5.0.0 available for MediaWiki 1.34+.

Since MediaWiki update from 1.36.2 to 1.37.1 I see on top of my Wiki the following debug messages caused by Matomo extension:

Use of $wgUser was deprecated in MediaWiki 1.35. [Called from MatomoHooks::MatomoSetup in ***/extensions/matomo/Matomo.hooks.php at line 23] in ***/includes/debug/MWDebug.php on line 375

$wgUser reassignment detected [Called from MatomoHooks::MatomoSetup in ***/extensions/matomo/Matomo.hooks.php at line 23] in ***/includes/debug/MWDebug.php on line 375

Matomo ext. version 4.01

Any hint how to avoid or is an extsntion updated planned?

Thanks!

see: github.com/DaSchTour/matomo-mediawiki-extension/issues/38

I added a pull request to the git repository. The issue is in line 173 of the matomo.hooks / hooks.php (file name depends if you install from composer or git). isLoggedIn() is deprecated and ! isAnon() needs to be used. After i did I realized there is another pull request in there already for this. So the trick would be to get the owner to merge one or the other or to come up with their preferred solution and then also update the composer. Depending if that's what should be used to install this. The install instructions really don't mention composer for this, so I wonder where that repository came from.

This is fixed in version 5.0.0 available for MediaWiki 1.34+.

Fixed in version 5.0.0 available for MediaWiki 1.34+.

Plugin not compatible

Fatal error: Call to undefined function isLoggedIn()

This is fixed in version 5.0.0 available for MediaWiki 1.34+.

On packagist.org I can read: This package is not auto-updated. Last update: 2021-02-26 06:29:03 UTC

The latest version is there but I guess it will be preferable to setup up auto-updating to assure that the latest releases also end up over there.

There is no auto-update feature within MediaWiki extensions the closes to auto updating is to use composer and run the script frequently. Also this was last updated back in 2019.

Thanks for your reply. However I am talking about auto-updating latest code to packagist to actually be able to do the very thing you are suggesting. :)

The version on packagist list is the same version that is on github

I know, however the code on packagist.org will not be updated if there is a new version. I am not sure if you read my message.

I got the same message, what will be the solution?