Thomas

@knut2 I was able to reproduce it that way. Installed WP-Matomo, Configured PHP mode, enabled WordPress toolbar. Then WP-Matomo was loading the other Matomo and this causes issues. I have changed our system report to hopefully detect this use case in the future and show a warning right away. Be great if you could double check and confirm this behaviour and ideally mark the support thread as resolved. Hoping this helps.

@tanrim Do you still see this error? Was Matomo installed successfully? If you see this only during installation this might be expected.

If you still see this error, and you can view the system report in the WordPress Dashboard => Matomo Analytics => System Report
could you send us the anonymised system report from the beginning of that page to wordpress at matomo dot org? If it fails to load the system report page, you may need to enable the safe mode see : https://matomo.org/faq/wordpress/i-have-a-problem-how-do-i-troubleshoot-and-enable-wp_debug/

By adding this to your wp-config.php

define( ‘MATOMO_SAFE_MODE’, true );

Awesome, thanks for letting me know. Glad it works now. And thank you for the wp_normalize_path hint, I’ll look into this now. Very appreciated.

Thanks for letting us know @apedog

I’ll adjust the plugin check cause currently we’re only checking for ABSPATH . 'wp-content' === rtrim( WP_CONTENT_DIR, '/' )). So basically we’re checking for ABSPATH . 'wp-content' and not also for ABSPATH . '/wp-content'.

Re define( 'MATOMO_WP_ROOT_PATH', ABSPATH ) for some reason we’re currently only supporting this as an environment variable but not as a constant. I will have a look later regarding the reason.

I will start working on a patch and see what is happening in https://github.com/matomo-org/wp-matomo/pull/223

Maybe you could define content directory as ABSPATH . 'wp-content' to fix it?

@knut2

Thanks for creating the issue!

Is there any chance you could paste the anonymised system report here or email it to us to wordpress at matomo.org ?

See
https://matomo.org/faq/wordpress/i-have-a-problem-how-do-i-troubleshoot-and-enable-wp_debug/

You will probably need to add this to your wp-config.php:

define( 'MATOMO_SAFE_MODE', true );

In order to avoid above error you are currently getting.

It seems like that Matomo config is maybe not loaded cause it should not use that Zend DB but WordPress DB.

Do you get this error directly after activating the plugin @knut2 ? Do you know if you see in the WordPress Dashboard the Matomo Analytics menu item?

@benbois Apologies for that. Only one part of the readme was correctly updated but I forgot to update the other part in the description where it falsely says PHP 7.0

The plugin would actually work perfectly fine on PHP 7.0. However, in a few months we will be releasing a new major update where we already know we will require PHP 7.2. We found it would be unfair to get many installs from users using PHP 7.0 and PHP 7.1 and then a few months later they wouldn’t be able to receive an update anymore. This is why we decided to directly require PHP 7.2 even though it would work with PHP 7.0.

If you still want to use it in the meantime, you could technically change the value in the wp-content/plugins/matomo/readme.txt to Requires PHP: 7.0 and you could use it. However, in say 4-5 months time there will be an update requiring PHP 7.2 and you would need to make that change in the readme.txt after each update so I suppose this is not really a solution.

If there’s any chance, it be great if you could update your PHP version considering it’s a not supported version anymore. I’m fully aware this is not always easy, and sometimes not even possible.

BTW I have added more information to our FAQ: https://matomo.org/faq/wordpress/how-do-i-install-matomo-for-wordpress/ You can see the related PHP settings at the bottom of that page if that’s something you’re keen on.

Does that help you? Be great to mark it as resolved if so.

@duracelltomi

Totally aware of what you’re seeing and understand. Just btw there are a few more things that Matomo does by default which others maybe don’t like anonymising IP. Matomo can also easily configured without cookies. You can configure raw and reporting data retention to automatically eg delete raw data after 30 days, you can automatically anonymise various data and the same data is not used for any other purpose (like some others do) and not shared with a third party. There are also heaps of other ways to protect privacy etc. which other tools might not have.

Also need to differentiate between cookie consent and tracking consent.
There are some recommendations from institutions out there (eg in France and Berlin and I think other places) that you wouldn’t need to ask for tracking consent with Matomo and possibly not even for cookie consent in some cases. See eg https://www.datenschutz-berlin.de/fileadmin/user_upload/pdf/pressemitteilungen/2019/20191114-PM-Analyse_Trackingtools.pdf

Really appreciate your comment, it’s a complex story as we all know. And as long as you don’t track personal data you wouldn’t need the tracking consent. As for the cookie consent it may be needed, we’ll be working though on something that you won’t need it for sure (no fingerprinting etc).