pluto11

Here’s the screenshot.

Thanks so much for the fix in version 5.6.1. Everything looks fine except that when I choose a 3 or 4-column layout for the dashboard, I get a 2-column layout. Below is the current System Report.

              # Matomo

• Matomo Plugin Version: 5.6.1
• Config exists and is writable.: Yes (“$WP_CONTENT_DIR//uploads/matomo/config/config.ini.php” )
• JS Tracker exists and is writable.: Yes (“$WP_CONTENT_DIR//uploads/matomo/matomo.js” )
• Plugin directories: Yes ([{“pluginsPathAbsolute”:”\/srv\/htdocs\/wp-content\/plugins\/matomo\/plugins”,”webrootDirRelativeToMatomo”:”..\/plugins”}])
• Tmp directory writable: Yes ($WP_CONTENT_DIR//cache/matomo)
• Matomo Version: 5.6.2
• Matomo Blog idSite: 1
• Matomo Install Version: 5.3.3 (Install date: 2025-12-05 15:47:51)
• Upgrades outstanding: No
• Upgrade in progress: No
• Current Matomo User Language: en
• Current Matomo Language Cookie Value: None

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

• Server time: 2026-01-25 21:35:22
• Blog time: 2026-01-25 16:35:22 (Below dates are shown in blog timezone)
• Sync users & sites: Next run: 2026-01-26 15:48:44 (23 hours 13 min) ( Last started: 2026-01-25 16:22:38 (-12 min 44s). Last ended: 2026-01-25 16:22:38 (-12 min 44s). Interval: daily)
• Archive: Next run: 2026-01-25 16:47:52 (12 min 30s) ( Last started: 2026-01-25 16:22:34 (-12 min 48s). Last ended: 2026-01-25 16:22:38 (-12 min 44s). Interval: hourly)
• Update GeoIP DB: Next run: 2026-02-03 15:48:42 (8 days 23 hours) ( Last started: 2026-01-04 16:10:23 (-21 days 0 hours). Last ended: 2026-01-04 16:10:27 (-21 days 0 hours). Interval: matomo_monthly)

Mandatory checks

• PHP version >= 7.2.5: ok
• PDO extension: ok
• PDO\MYSQL extension: ok
• MYSQLI extension: ok
• Other required extensions: ok
• Required functions: ok
• Required PHP configuration (php.ini): ok
• Directories with write access: ok
• Directories with write access for Tag Manager: ok

Optional checks

• 64-bit PHP Binary: ok
• Tracker status: ok
• Memory limit: ok
• Time zone: ok
• Open URL: ok
• GD > 2.x + FreeType (graphics): ok
• Other extensions: ok
• Other functions: ok
• Filesystem: ok
• Last Successful Archiving Completion: ok
• Warning Database abilities: warning (UTF8mb4 charset Your database supports utf8mb4 charset, but your database tables have not been converted yet. You can do this by executing the command $WP_CONTENT_DIR//plugins/matomo/app/console core:convert-to-utf8mb4 or activating the automatic conversion in General Settings. This is required to be able to store 4-byte UTF8 characters. Unless utf8mb4 is available special characters, such as emojis, less common characters of asian languages, various historic scripts or mathematical symbols will be replaced with �. You can read more details about this topic in this FAQ. Connection collation CREATE TEMPORARY TABLES Changing transaction isolation level Your database version indicates you might be using a MariaDb server. If this is the case, please ensure to set [database] schema = Mariadb in the “config/config.ini.php” file, to ensure all database feature work as expected. )
• Max Packet Size: ok
• Geolocation: ok
• Update over HTTPS: ok
• Mobile Messaging SMS Provider: ok
• Supports Async Archiving: No
• Async Archiving Disabled in Setting: No
• Location provider ID: geoip2php
• Location provider available: Yes
• Location provider working: Yes
• Warning Proxy header: HTTP_X_FORWARDED_FOR (A proxy header is set which means you maybe need to configure a proxy header in the Advanced settings to make location reporting work. If the location in your reports is detected correctly, you can ignore this warning. Learn more)
• Had visit in last 5 days: Yes
• Matomo URL: Yes ($site_url/wp-content/plugins/matomo/app/)
• Warning YML files should not be accessible: warning (The .yml files in the wp-content/plugins/matomo/app/vendor directory are accessible from the internet. This can cause some web security tools to flag your website as suspicious. If you are using Apache, it is probably due to your server configuration disabling the use of .htaccess files. If you are instead using nginx, it is due to your nginx configuration allowing .yml files. You may need to contact your hosting provider to fix this.)

Matomo Settings

• Track mode: disabled
• Track ecommerce: Yes
• Track codeposition: footer
• Track api endpoint: default
• Track js endpoint: default
• Version history: 5.6.1, 5.6.0, 5.3.3
• Core version: 5.6.2
• Last tracking settings update: 1764967774
• Last settings update: 1766255847
• Mail history: 2026-01-19 01:00:09, 2026-01-12 00:49:47, 2026-01-05 00:49:22

Logs

• None:

WordPress

• Home URL: $site_url
• Site URL: $site_url
• WordPress Version: 6.9
• Number of blogs: 1
• Multisite Enabled: No
• Network Enabled: No
• WP_DEBUG: No
• WP_DEBUG_DISPLAY: No
• WP_DEBUG_LOG: No
• DISABLE_WP_CRON: –
• FORCE_SSL_ADMIN: No
• WP_CACHE: Yes
• CONCATENATE_SCRIPTS: –
• COMPRESS_SCRIPTS: –
• COMPRESS_CSS: –
• ENFORCE_GZIP: –
• WP_LOCAL_DEV: –
• WP_CONTENT_URL: $site_url/wp-content
• WP_CONTENT_DIR: $WP_CONTENT_DIR/
• UPLOADS: –
• BLOGUPLOADDIR: –
• DIEONDBERROR: –
• WPLANG: –
• ALTERNATE_WP_CRON: –
• WP_CRON_LOCK_TIMEOUT: 60
• WP_DISABLE_FATAL_ERROR_HANDLER: –
• MATOMO_SUPPORT_ASYNC_ARCHIVING: –
• MATOMO_ENABLE_TAG_MANAGER: –
• MATOMO_SUPPRESS_DB_ERRORS: –
• MATOMO_ENABLE_AUTO_UPGRADE: –
• MATOMO_DEBUG: –
• MATOMO_SAFE_MODE: –
• MATOMO_GLOBAL_UPLOAD_DIR: –
• MATOMO_LOGIN_REDIRECT: –
• Permalink Structure: /%year%/%monthnum%/%day%/%postname%/
• Possibly uses symlink: No
• Upload base url: $site_url/wp-content/uploads
• Upload base dir: $WP_CONTENT_DIR//uploads
• Upload url: $site_url/wp-content/uploads/2026/01
• Custom upload_path:
• Custom upload_url_path:
• Compatible content directory: Yes
• WP_Filesystem Initialized: Yes
• Warning System Cron Set Up: No (Warning: Your WordPress site does not appear to have a system cron job set up to run the WordPress cron. Matomo uses the WordPress cron to generate reports and to delete temporary data to provide compliance with various privacy regulations (e.g., GDPR). Without a system cron job set up, these tasks may be run irregularly or infrequently, which could lead to personal data being retained longer than allowed. To avoid this, we recommend setting up a system cron job to run the WordPress cron regularly. Contact your hosting provider if you require help with this.)
• Current User Locale: en_US

WordPress Plugins MU Plugins

• wpcomsh-loader.php:

Plugins

• Akismet Anti-spam: Spam Protection: 5.6
• All in One SEO: 4.9.3
• Classic Editor: 1.6.7
• Complianz Privacy Suite (GDPR/CCPA) premium: 7.5.6.1
• Crowdsignal Forms: 1.7.2
• Crowdsignal Polls & Ratings: 3.1.4
• Duplicator: 1.5.14 (Network enabled)
• Gravatar Enhanced: 0.13.0
• Gutenberg: 22.4.0
• Jetpack: 15.5-a.3
• Layout Grid: 1.8.5
• Matomo Analytics – Ethical Stats. Powerful Insights.: 5.6.1
• Page Optimize: 0.5.8
• WPConsent: 1.1.3
• WPForms Lite: 1.9.8.7
• Active Plugins: 13 (akismet:5.6 all-in-one-seo-pack:4.9.3 complianz-gdpr-premium:7.5.6.1 crowdsignal-forms:1.7.2 gravatar-enhanced:0.13.0 gutenberg:22.4.0 jetpack:15.5-a.3 layout-grid:1.8.5 matomo:5.6.1 page-optimize:0.5.8 polldaddy:3.1.4 wpconsent-cookies-banner-privacy-suite:1.1.3 wpforms-lite:1.9.8.7)
• Theme: twentytwentythree (twentytwentythree)

Server

• Server Info: nginx
• PHP OS: Linux
• PHP Version: 8.3.30
• PHP SAPI: fpm-fcgi
• PHP Binary Name: /root/roles/nginx-php/usr/local/php8.3/bin.bookworm/php-fpm
• PHP Maxmind DB extension: Not loaded
• PHP Error Reporting: After bootstrap: 4437
• Timezone: UTC
• WP timezone: America/Jamaica
• Locale: en_US
• User Locale: en_US
• Memory Limit: 512M (At least 128MB recommended. Depending on your traffic 256MB or more may be needed.)
• WP Memory Limit: 512M
• WP Max Memory Limit: 512M
• Timezone version: 2025.2
• Time: 1769376922
• Max Execution Time: 850
• Max Post Size: 2047M
• Max Upload Size: 2146435072
• Max Input Vars: 6144
• Disabled PHP functions: Yes (pcntl_fork)
• zlib.output_compression is off: Yes
• Curl Version: 8.18.0, OpenSSL/3.0.18
• Suhosin installed: No

PHP cli

• PHP CLI Version: (The detected PHP CLI version does not match the PHP web version. To avoid archiving errors, enable archiving via HTTP requests, or manually set the path to your PHP CLI executable to the one for PHP version 8.3.30.)
• MySQLi support: missing (Your PHP cli does not load the MySQLi extension. You might have archiving problems in Matomo but also others problems in your WordPress cron tasks. You should enable this extension)

Database

• MySQL Version: 11.4.9
• Mysqli Connect: Yes
• Force MySQL over Mysqli: No
• DB Prefix: wp_
• DB CHARSET: latin1
• DB COLLATE: latin1_swedish_ci
• SHOW ERRORS: No
• SUPPRESS ERRORS: No
• Uses Socket: No
• Uses IPv6: No
• Matomo tables found: 104
• DB tables exist: Yes
• Matomo users found: 1
• Matomo sites found: 1
• Required permissions: OK

Browser

• Browser: (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36)
• Language: en-us,en

I am using Matomo Analytics for WordPress on a Windows 10 laptop with screen resolution 1920 x 1080. Matomo is configured for consent-based tracking by following the instructions in the article https://matomo.org/faq/how-to/using-complianz-for-wordpress-consent-manager-with-matomo/ Tested that Complianz is working as per instructions in the article and it is setting cookies as expected. The Matomo Analytics > Reporting dashboard has always displayed as a single column ever since the Matomo plugin was activated on WordPress.