Error after upgrade 4.0.4 (E_COMPILE_ERROR)

[mthchz]

Hello,

Since the 4.0.4 update I’ve a total outage of WP Matomo :

Une erreur de type E_COMPILE_ERROR a été causée dans la ligne 135 du fichier /home/imysvyy/www/wp-content/plugins/matomo/app/vendor/php-di/php-di/src/Definition/Helper/CreateDefinitionHelper.php. Message d’erreur : Declaration of DI\Definition\Helper\CreateDefinitionHelper::getDefinition(string $entryName): DI\Definition\Definition must be compatible with DI\Definition\Helper\DefinitionHelper::getDefinition($entryName)

I’ve trying PHP 8.0 instead 7.3 but it’s not better…

Here my system report : 

Matomo

• Version de l’extension Matomo: 4.0.4
• Config existe et est accessible en écriture.: Oui ("$ABSPATH/wp-content/uploads/matomo/config/config.ini.php" )
• JS Tracker existe et est accessible en écriture.: Oui ("$ABSPATH/wp-content/uploads/matomo/matomo.js" )
• Répertoires de l4extension: Yes ([{"pluginsPathAbsolute":"$ABSPATH/wp-content/plugins/matomo/plugins","webrootDirRelativeToMatomo":"../"}])
• Répertoire temporaire non accessible en écriture: Yes ($ABSPATH/wp-content/cache/matomo)
• Matomo site idSite: 1
• Matomo Install Version: No (Install date: 2020-05-11 22:20:02)

Endpoints

• Matomo JavaScript Tracker URL:  ($site_url/wp-content/uploads/matomo/matomo.js)
• Matomo JavaScript Tracker - WP Rest API:  ($site_url/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/wp-json/matomo/v1/hit/)

Crons

• Heure du serveur: 2020-12-16 14:55:37
• Heure du site Web: 2020-12-16 15:55:37 (Les dates ci-dessous sont affichées dans le fuseau horaire du site Web)
• Sync users & sites: Next run: 2020-12-16 21:20:01 ( Last started: 2020-12-13 21:20:27. Last ended: 2020-12-13 21:20:27. Interval: daily)
• Archive: Next run: 2020-12-16 16:20:01 ( Last started: 2020-12-15 10:20:27. Last ended: 2020-12-14 15:20:37. Interval: hourly)
• Update GeoIP DB: Next run: 2021-01-06 21:20:01 ( Last started: 2020-12-07 21:42:23. Last ended: 2020-12-07 21:42:26. Interval: matomo_monthly)

Matomo Settings

• Track mode: manually
• Track codeposition: footer
• Track api endpoint: default
• Track js endpoint: default
• Version history: 1.3.2, 1.0.6, 1.0.5
• Core version: 3.14.0
• Last tracking settings update: 1605647183
• Last settings update: 1605784267
• Track ecommerce: No
• Track 404: Yes
• Show get started page: 0

Logs

• Warning archive_bootstrap: 2020-12-15 10:20:27 (Your Matomo codebase is running the old version 3.13.5 and we have detected that your Matomo Database has already been upgraded to the newer version 3.14.0. Maybe your Matomo administrators are currently finishing the upgrade process. Please try again in a few minutes. If you still have this issue please contact your Matomo administrator for assistance.  => FrontController.php:645; FrontController.php:376; Bootstrap.php:78; Bootstrap.php:104; ScheduledTasks.php:193; class-wp-hook.php:285; class-wp-hook.php:311; plugin.php:551; wp-cron.php:138;)

WordPress

• Home URL: $site_url
• Site URL: $site_url
• WordPress Version: 5.6
• 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: -
• MATOMO_SUPPORT_ASYNC_ARCHIVING: -
• MATOMO_TRIGGER_BROWSER_ARCHIVING: -
• MATOMO_ENABLE_TAG_MANAGER: -
• MATOMO_SUPPRESS_DB_ERRORS: -
• MATOMO_ENABLE_AUTO_UPGRADE: -
• MATOMO_DEBUG: -
• MATOMO_SAFE_MODE: Yes
• MATOMO_GLOBAL_UPLOAD_DIR: -
• MATOMO_LOGIN_REDIRECT: -
• Permalink Structure: /%postname%/
• Possibly uses symlink: No
• Compatible content directory: Yes

WordPress Plugins

• Branda Pro: 3.4.1
• Defender Pro: 2.4.4 (Network enabled)
• Forminator Pro: 1.14.6
• Hummingbird Pro: 2.7.0 (Network enabled)
• Matomo Analytics - Ethical Stats. Powerful Insights.: 4.0.4
• Redirection: 4.9.2
• SmartCrawl Pro: 2.8.4 (Network enabled)
• Smush Pro: 3.8.2
• Snapshot Pro: 4.1.2 (Network enabled)
• WP Featherlight: 1.3.4
• WPMU DEV Dashboard: 4.10.6 (Network enabled)
• Active Plugins: 11 (forminator matomo redirection snapshot-backups ultimate-branding wp-defender wp-featherlight wp-hummingbird wp-smush-pro wpmu-dev-seo wpmudev-updates)

Server

• Server Info: Apache
• PHP OS: Linux
• PHP Version: 8.0.0RC4
• PHP SAPI: fpm-fcgi
• PHP Binary Name: php-fpm
• Timezone: UTC
• WP timezone: Europe/Paris
• Locale: fr_FR
• User Locale: fr_FR
• Memory Limit: 512M (At least 128MB recommended. Depending on your traffic 256MB or more may be needed.)
• WP Memory Limit: 40M
• WP Max Memory Limit: 512M
• Timezone version: 2020.4
• Time: 1608130537
• Max Execution Time: 165
• Max Post Size: 130M
• Max Upload Size: 134217728
• Max Input Vars: 16000
• Disabled PHP functions: Yes (_dyuweyrj4,_dyuweyrj4r,dl)
• zlib.output_compression is off: Yes
• Curl Version: 7.64.0, OpenSSL/1.1.1d
• Suhosin installed: No

Database

• MySQL Version: 5.6.50
• Mysqli Connect: Yes
• Force MySQL over Mysqli: No
• DB CHARSET: utf8
• DB COLLATE: 
• SHOW ERRORS: No
• SUPPRESS ERRORS: No
• Uses Socket: No
• Uses IPv6: No
• Matomo tables found: 61
• Matomo users found: 2
• Matomo sites found: 1
• Permissions requises: OK

Browser

• Browser:  (Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:84.0) Gecko/20100101 Firefox/84.0

[Findus23]

Hi,

This sounds very similar to https://forum.matomo.org/t/e-compile-error/39569/13 and might be caused by another one of the other plugins you use depending on an older version of a library Matomo uses.
If you can try it out, maybe try disabling them one-by-one until you see the one with the collision.

[sgiehl]

Also see #233

[mthchz]

Hi,

This sounds very similar to https://forum.matomo.org/t/e-compile-error/39569/13 and might be caused by another one of the other plugins you use depending on an older version of a library Matomo uses.
If you can try it out, maybe try disabling them one-by-one until you see the one with the collision.

Ok, thank you!
This is Defender Pro by WPMU DEV.

[mthchz]

Topic open on the WPMUDev support forum : https://premium.wpmudev.org/forums/topic/defender-pro-defenders-dependency-crash-wp-matomo-4-0-4/

[tsteur]

@mthchz can you confirm Matomo works when you disable WP defender? I don't have an up to date version of the plugin here but an earlier version I think seems to have worked with Matomo. Possible though they started using it recently. Be great to let us know when they change something. For now I'll mark the plugin as incompatible so Matomo won't start when that plugin is installed.

[tsteur]

I'll actually wait for your confirmation that it is indeed caused by that plugin @mthchz

[mthchz]

@mthchz can you confirm Matomo works when you disable WP defender? I don't have an up to date version of the plugin here but an earlier version I think seems to have worked with Matomo. Possible though they started using it recently. Be great to let us know when they change something. For now I'll mark the plugin as incompatible so Matomo won't start when that plugin is installed.

@tsteur Yes, I confirm that. WP Matomo (v4.0.4) work with WP Defender Pro (v2.4.4) disabled

[tsteur]

Thanks for confirming. I will put our plugin into safe mode in future when WP defender is used until they have a fix for it. If you ever hear from them re having a fix that be great to let us know.

#401

[mthchz]

Hi there,

The WPMUDev Defender Pro seem to be updated for PHP 8 compatibility

Can I test them on my site by forcing the safe_mode to be deactivated? (Currently define ('MATOMO_SAFE_MODE', false); does not work)

[tsteur]

Hi @mthchz any chance you could apply this same change from 6e46c21 to the file in wp-content/plugins/matomo/classes/WpMatomo.php ? This would allow you to force safe mode to be disabled. You could otherwise also simply change return true; to return false; in that line 174.

[jicao]

Hello,

We've open a ticket to WPMUDEV for "this issue" with WP Defender Pro here https://wpmudev.com/forums/topic/defender-pro-defender-pro-and-matomo-analytics/#post-4062481

It seems that this is a matter of compatibility as Defender is also supporting older PHP versions like v.5.6. This is happening cause we still support all PHP versions that are listed in the WP requirements. Unfortunately, there’s no workaround for the current state, as that would bring performance issues to our plugins as it would make many checks for that specific Matomo plugin.

Hope they'll forget about PHP 5.6 asap... EOL December 18...