Marketing Campaigns Reporting (Matomo Plugin) leads to critical error

After Upgrading Matomo Analytics for Wordpress to 1.3, the entire wp-admin section is broken (the classic “critical error” screen shows up). The website itself get’s displayed without any errors, only administration area of wordpress itself can’t be loaded anymore.

As a “quick and dirty” fix I’ve disabled the “Matomo Campaings Reporting” Plugin within Wordpress (rename “plugins” folder within wordpress-install to “pluginsOff”, open the admin-area of wordpress and go to plugins (this will disable them all in the background). Rename the “pluginsOff” again to “plugins” and start enable one plugin after another to test).
Result: wordpress admin area is running again until you active the “Marketing Campaigns Reporting” Plugin in Wordpress-Backend. If you enable it, the critical error occurs again.

Does anyone had any similar problems or anything like this when upgrading to 1.3.0 ? I’m not able to reproduce this in my lab-environment, but I have to say that the lab-environment is not an exact copy of the website (hoster is using litespeed-webserver, my lab using the litespeed opensource server, configs of webserver might differ, no cache plugin in dev-environment (thus the same error happens in prod-environment if I disable cache) and it’s own wordpress-database which wasn’t copied from production).

Please note: I’m a sysadmin, so if there is any developer who wants to investigat this further please declare what kind of logfiles etc. you need. Since it is a productive environment where this happens, I would have to re-enable the marketplace plugin during off-hours (GMT+2)

				  # Matomo

* Matomo Plugin Version: 1.3.0
* Config exists and is writable.: Yes ("$ABSPATH/wp-content/uploads/matomo/config/config.ini.php" )
* JS Tracker exists and is writable.: Yes ("$ABSPATH/wp-content/uploads/matomo/matomo.js" )
* Plugin directories: Yes ([{"pluginsPathAbsolute":"$ABSPATH\/wp-content\/plugins\/matomo\/plugins","webrootDirRelativeToMatomo":"..\/"},{"pluginsPathAbsolute":"$ABSPATH\/wp-content\/plugins","webrootDirRelativeToMatomo":"..\/..\/"}])
* Tmp directory writable: Yes ($ABSPATH/wp-content/cache/matomo)
* Matomo Version: 3.14.0
* Matomo Blog idSite: 1
* Matomo Install Version: No

## Endpoints

* Matomo JavaScript Tracker URL:  ($site_url/wp-content/uploads/matomo/matomo.js)
* Matomo JavaScript Tracker - WP Rest API:  ($site_url/index.php/wp-json/matomo/v1/hit/)
* Matomo HTTP Tracking API:  ($site_url/wp-content/plugins/matomo/app/matomo.php)
* Matomo HTTP Tracking API - WP Rest API:  ($site_url/index.php/wp-json/matomo/v1/hit/)

## Crons

* Server time: 2020-09-03 16:43:26
* Blog time: 2020-09-03 17:43:26 (Below dates are shown in blog timezone)
* Sync users & sites: Next run: 2020-09-04 02:15:15 (8 Stunden 31 Minuten) ( Last started: 2020-09-03 02:29:33 (-15 Stunden 13 Minuten). Last ended: 2020-09-03 02:29:34 (-15 Stunden 13 Minuten). Interval: daily)
* Archive: Next run: 2020-09-03 18:15:15 (31 Minuten 49s) ( Last started: 2020-09-03 17:22:03 (-21 Minuten 23s). Last ended: 2020-09-03 11:21:58 (-6 Stunden 21 Minuten). Interval: hourly)
* Update GeoIP DB: Next run: 2020-09-29 04:41:18 (25 Tage 10 Stunden) ( Last started: 2020-08-30 05:05:46 (-4 Tage 12 Stunden). Last ended: 2020-03-26 02:19:30 (-161 Tage 15 Stunden). Interval: matomo_monthly)

## Mandatory checks

* PHP-Version >= : ok 
* PDO Erweiterung: ok 
* PDO\MYSQL Erweiterung: ok 
* MYSQLI Erweiterung: ok 
* Weitere erforderliche Anforderungen: ok 
* Erforderliche Funktionen: ok 
* Benötigte PHP Konfiguration (php.ini): ok 
* Verzeichnisse mit Schreibzugriff: ok 
* Verzeichnisse mit Schreibzugriff auf Tag Manager: ok 

## Optional checks

* Tracker-Status: ok 
* Speicherlimit: ok 
* Zeitzone: ok 
* Öffnen einer URL: ok 
* PageSpeed deaktiviert: ok 
* GD > 2.x + Freetype (graphics): ok 
* Andere Erweiterungen: ok 
* Warning Andere Funktionen: warning  (shell_exec Sie müssen diese eingebaute Funktion aktivieren set_time_limit mail parse_ini_file glob gzopen md5_file )
* Dateisystem: ok 
* Archiv Cron: ok 
* Letzter erfolgreicher Abschluss der Archivierung: ok 
* Maximale Packetgröße: ok 
* Standorterkennung: ok 
* Update über HTTPS: ok 
* Schreibbarer JavaScript-Tracker ("/matomo.js"): ok 
* Supports Async Archiving: No
* Location provider ID: geoip2php
* Location provider available: Yes
* Location provider working: Yes
* Had visit in last 5 days: Yes

## Matomo Settings

* Track mode: default
* Track codeposition: footer
* Track api endpoint: default
* Track js endpoint: default
* Version history: 1.3.0, 1.2.0, 1.1.3, 1.1.2, 1.1.1
* Core version: 3.14.0
* Last tracking settings update: 1590897100
* Last settings update: 1590897100
* Track content: visible
* Track ecommerce: No
* Track 404: Yes
* Show get started page: 0

## Logs

* update_geoip2: 2020-08-30 05:05:47 (GeoIP2AutoUpdater: failed to unzip '$ABSPATH/wp-content/cache/matomo/latest/GeoIP2-City.mmdb.tar.gz' after downloading 'https://download.maxmind.com/app/geoip_download?edition_id=GeoLite2-City&suffix=tar.gz&license_key=okI8j1UHemAhs': Couldn't list content for '$ABSPATH/wp-content/cache/matomo/latest/GeoIP2-City.mmdb.tar.gz': Invalid block size : 20 => GeoIP2AutoUpdater.php:172; GeoIP2AutoUpdater.php:99; ScheduledTasks.php:161; class-wp-hook.php:285; class-wp-hook.php:311; plugin.php:544; wp-cron.php:138;)

# WordPress

* Home URL: $site_url
* Site URL: $site_url
* WordPress Version: 5.5.1
* Number of blogs: 1
* Multisite Enabled: No
* Network Enabled: No
* WP_DEBUG: No
* WP_DEBUG_DISPLAY: Yes
* WP_DEBUG_LOG: No
* DISABLE_WP_CRON: -
* FORCE_SSL_ADMIN: Yes
* WP_CACHE: Yes
* CONCATENATE_SCRIPTS: -
* COMPRESS_SCRIPTS: -
* COMPRESS_CSS: -
* ENFORCE_GZIP: -
* WP_LOCAL_DEV: -
* DIEONDBERROR: -
* WPLANG: -
* ALTERNATE_WP_CRON: -
* WP_CRON_LOCK_TIMEOUT: 60
* WP_DISABLE_FATAL_ERROR_HANDLER: -
* Permalink Structure: /index.php/%year%/%monthnum%/%day%/%postname%/
* Possibly uses symlink: No
* Compatible content directory: Yes

# WordPress Plugins

* Contact Form 7: 5.2.2
* Cookie Notice: 1.3.2
* Google XML Sitemaps: 4.1.1
* IPtoCompany (Matomo Plugin): 0.4.5
* LiteSpeed Cache: 3.4.1
* Marketing Campaigns Reporting (Matomo Plugin): 4.0.1
* Matomo Analytics - Ethical Stats. Powerful Insights.: 1.3.0
* Matomo Marketplace for WordPress: 1.0.6
* Rank Math SEO: 1.0.47.1
* Active Plugins: 8 (IPtoCompany contact-form-7 cookie-notice google-sitemap-generator litespeed-cache matomo-marketplace-for-wordpress matomo seo-by-rank-math)

# Server

* Server Info: LiteSpeed
* PHP OS: Linux
* PHP Version: 7.4.8
* PHP SAPI: litespeed
* PHP Binary Name: lsphp
* PHP Found Binary: php -q
* Timezone: UTC
* WP timezone: +01:00
* Locale: de_CH
* User Locale: de_CH
* Memory Limit: 256M (At least 128MB recommended. Depending on your traffic 256MB or more may be needed.)
* WP Memory Limit: 64M
* WP Max Memory Limit: 256M
* Time: 1599151406
* Max Execution Time: 30
* Max Post Size: 16M
* Max Upload Size: 16777216
* Max Input Vars: 1000
* Disabled PHP functions: Yes (exec, shell_exec, system, dl, passthru, proc_open, proc_close)
* zlib.output_compression is off: Yes
* Curl Version: 7.62.0, OpenSSL/1.0.2k
* Suhosin installed: No

# Database

* MySQL Version: 5.7.26
* Mysqli Connect: Yes
* Force MySQL over Mysqli: No
* DB Prefix: wp_
* DB CHARSET: utf8mb4
* DB COLLATE: 
* SHOW ERRORS: No
* SUPPRESS ERRORS: No
* Uses Socket: No
* Uses IPv6: No
* Matomo tables found: 126
* Matomo users found: 2
* Matomo sites found: 1
* Required permissions: OK

# Browser

* Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Firefox/78.0
* Language: de,en-us,en

	

Hi,

It would be great if you could check if there was an error in the PHP error log.

Hi @sysguy

the Matomo for WordPress Marketplace plugin was falsely sending you an update to a plugin that is only compatible with the next major version of Matomo (Matomo 4 vs currently Matomo 3 is used).

To solve this problem there are two ways:

Let me know if you need help with any of this.

We have also released an update for Matomo Marketplace for WordPress plugin to prevent this issue in the future.

Hi Thomas,

Thanks for your reply. Replaced it manually and worked without any issues.