plugin-MarketingCampaignsReporting
plugin-MarketingCampaignsReporting copied to clipboard
No campaign data on WordPress with the latest plugin release
Campaign requests are empty
When requesting %wordpress_url%?mtm_campaign=2022_grundrauschen_dresden&mtm_placement=google#/Verf%C3%BCgbarkeitspr%C3%BCfung
, If I enable the campaign plugin and create a segment with campaign name = 2022_grundrauschen_dresden
and campaign placement = google
, I don't have any result.
Expected behaviour
See my visit in the visitor log after apply this segment.
step to reproduce
- install WordPress
- install the Matomo marketplace plugin
- go to the URL
wp-admin/admin.php?page=matomo-marketplace
- click on the download button under the Marketing Campaigns Reporting widget
- Move the content of the extracted folder into your WordPress wp-content/plugins directory
- Go to wp-admin/plugins.php
- Click on the activate link under "Marketing Campaigns Reporting (Matomo Plugin)"
- Go to your frontend website
- request the URL
?mtm_campaign=2022_grundrauschen_dresden&mtm_placement=google#/Verf%C3%BCgbarkeitspr%C3%BCfung
- Go to your Matomo when requesting
/wp-content/plugins/matomo/app/index.php?module=CoreHome&action=index&idSite=1&period=day&date=yesterday#?period=day&date=2022-09-28&idSite=1&category=General_Visitors&subcategory=Live_VisitorLog
- Check that the last visit (please update the date in the date picker) contains only campaign placement value
- Create a segment with campaign name = 2022_grundrauschen_dresden and campaign placement = google.
- Apply this segment
- Go to
wp-content/plugins/matomo/app/index.php?module=CoreHome&action=index&idSite=1&period=day&date=yesterday#?period=day&date=2022-09-28&segment=campaignName%3D%3D2022_grundrauschen_dresden;campaignPlacement%3D%3Dgoogle&idSite=1&category=General_Visitors&subcategory=Live_VisitorLog
for the current date and check there is no record in the visitor log. - Connect to your mysql database using the following command mysql -u %mysql_username% -p %mysql_database_name%
- Run this SQL query:
select * from wp_matomo_log_visit where campaign_name = '2022_grundrauschen_dresden' or campaign_placement = 'google'
. Remplace wp_ in the table name by your wordpress prefix available in the wp-config.php file. - Consider there are no record having both a campaign name and a campaign placement.
Context
WordPress Version | 6.0.2 Matomo Plugin Version | 4.11.0 Matomo Install Version | 4.6.0 Marketing Campaigns Reporting (Matomo Plugin) | 4.1.3 Firefox version | 104.0 (64-bit)
Full diagnostics report
` # Matomo
- Matomo Plugin Version: 4.11.0
- Config exists and is writable.: Yes ("$abs_path/wp-content/uploads/matomo/config/config.ini.php" )
- JS Tracker exists and is writable.: Yes ("$abs_path/wp-content/uploads/matomo/matomo.js" )
- Plugin directories: Yes ([{"pluginsPathAbsolute":"$abs_path/wp-content/plugins/matomo/plugins","webrootDirRelativeToMatomo":"../"},{"pluginsPathAbsolute":"$abs_path/wp-content/plugins","webrootDirRelativeToMatomo":"../../"}])
- Tmp directory writable: Yes ($abs_path/wp-content/cache/matomo)
- Matomo Version: 4.11.0
- Matomo Blog idSite: 1
- Matomo Install Version: 4.6.0 (Install date: 2022-04-20 10:19:01)
- Upgrades outstanding: No
- Upgrade in progress: No
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: 2022-09-28 00:50:25
- Blog time: 2022-09-28 00:50:25 (Below dates are shown in blog timezone)
- Sync users & sites: Next run: 2022-09-28 10:21:10 (9 hours 30 min) ( Last started: 2022-09-27 19:12:44 (-5 hours 37 min). Last ended: 2022-09-27 19:12:44 (-5 hours 37 min). Interval: daily)
- Archive: Next run: 2022-09-28 01:19:05 (28 min 40s) ( Last started: 2022-09-28 00:28:56 (-21 min 29s). Last ended: 2022-09-28 00:28:57 (-21 min 28s). Interval: hourly)
- Update GeoIP DB: Next run: 2022-10-17 10:21:10 (19 days 9 hours) ( Last started: 2022-09-18 21:11:20 (-9 days 3 hours). Last ended: 2022-09-18 21:11:25 (-9 days 3 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
- PageSpeed is turned off: ok
- GD > 2.x + FreeType (graphics): ok
- Other extensions: ok
- Other functions: ok
- Filesystem: ok
- Last Successful Archiving Completion: ok
- Database abilities: ok
- Max Packet Size: ok
- Geolocation: ok
- Update over HTTPS: ok
- Warning Heatmap & Session Recording Tracking: warning (Requesting '$site_url/wp-content/plugins/matomo/app/../../HeatmapSessionRecording/configs.php?idsite=1&trackerid=5lX6EM&url=http%3A%2F%2Ftest.test%2F' resulted in an SSL error. Maybe you are using a self signed certificate? Please open the URL manually in a browser to see if the response contains 'Piwik.HeatmapSessionRecording'. If not, you might need to modify your server configuration as this file needs to be accessible via a browser from the Internet or Intranet. )
- Supports Async Archiving: No
- Location provider ID: geoip2php
- Location provider available: Yes
- Location provider working: Yes
- Had visit in last 5 days: Yes
- Matomo URL: Yes ($site_url/wp-content/plugins/matomo/app/)
Matomo Settings
- Track mode: default
- Track codeposition: footer
- Track api endpoint: default
- Track js endpoint: default
- Version history: 4.11.0, 4.10.0, 4.9.0, 4.6.0
- Core version: 4.11.0
- Last tracking settings update: 1650450019
- Last settings update: 1660778286
- Mail history: 2022-09-26 19:04:47, 2022-09-21 20:41:02, 2022-09-14 00:51:53
- Delete all data uninstall: No
Logs
- mail_error: 2022-09-21 20:41:02 (Could not instantiate mail function. (has attachments) (type text/html) => Email.php:159; Email.php:69; Mail.php:292; ScheduledReports.php:435; EventDispatcher.php:141; Piwik.php:845; API.php:707; Context.php:75; API.php:719; Scheduler.php:309; Scheduler.php:154; API.php:68; CronArchive.php:653; CronArchive.php:279; Access.php:670; CronArchive.php:284; ScheduledTasks.php:332; class-wp-hook.php:305; class-wp-hook.php:331; plugin.php:524; wp-cron.php:138;)
- mail_error: 2022-09-26 19:04:47 (Could not instantiate mail function. (has attachments) (type text/html) => Email.php:159; Email.php:69; Mail.php:292; ScheduledReports.php:435; EventDispatcher.php:141; Piwik.php:845; API.php:707; Context.php:75; API.php:719; Scheduler.php:309; Scheduler.php:154; API.php:68; CronArchive.php:653; CronArchive.php:279; Access.php:670; CronArchive.php:284; ScheduledTasks.php:332; class-wp-hook.php:305; class-wp-hook.php:331; plugin.php:524; wp-cron.php:138;)
- ajax_tracker: 2022-09-26 19:05:43 (cURL error 60: SSL: no alternative certificate subject name matches target host name '$DB_USER.local' => AjaxTracker.php:91; MatomoTracker.php:793; Base.php:103; Woocommerce.php:176; Woocommerce.php:103; class-wp-hook.php:305; class-wp-hook.php:331; plugin.php:476; class-wc-cart.php:1276; class-wc-ajax.php:434; class-wp-hook.php:307; class-wp-hook.php:331; plugin.php:476; class-wc-ajax.php:93; class-wp-hook.php:307; class-wp-hook.php:331; plugin.php:476; template-loader.php:13; wp-blog-header.php:19; index.php:17;)
WordPress
- Home URL: $site_url
- Site URL: $site_url
- WordPress Version: 6.0.2
- Number of blogs: 1
- Multisite Enabled: No
- Network Enabled: No
- WP_DEBUG: Yes
- WP_DEBUG_DISPLAY: Yes
- WP_DEBUG_LOG: /tmp/wp.log
- DISABLE_WP_CRON: -
- FORCE_SSL_ADMIN: Yes
- WP_CACHE: Yes
- CONCATENATE_SCRIPTS: -
- COMPRESS_SCRIPTS: -
- COMPRESS_CSS: -
- ENFORCE_GZIP: -
- WP_LOCAL_DEV: -
- WP_CONTENT_URL: $site_url/wp-content
- WP_CONTENT_DIR: $abs_path/wp-content
- UPLOADS: -
- BLOGUPLOADDIR: -
- DIEONDBERROR: -
- WPLANG: -
- ALTERNATE_WP_CRON: -
- WP_CRON_LOCK_TIMEOUT: 60
- WP_DISABLE_FATAL_ERROR_HANDLER: -
- MATOMO_SUPPORT_ASYNC_ARCHIVING: No
- MATOMO_TRIGGER_BROWSER_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%/%postname%/
- Possibly uses symlink: No
- Upload base url: $site_url/wp-content/uploads
- Upload base dir: $abs_path/wp-content/uploads
- Upload url: $site_url/wp-content/uploads/2022/09
- Custom upload_path:
- Custom upload_url_path:
- Compatible content directory: Yes
WordPress Plugins
- Admin Notification (Matomo Plugin): 4.0.0
- Custom Reports (Matomo Plugin): 4.0.15
- Funnels (Matomo Plugin): 4.0.7
- Heatmap & Session Recording for Matomo: 4.5.0
- Marketing Campaigns Reporting (Matomo Plugin): 4.1.3
- Matomo Analytics - Ethical Stats. Powerful Insights.: 4.11.0
- Matomo Marketplace for WordPress: 1.0.10
- Query Monitor: 3.10.1
- Search Engine Keywords Performance (Matomo Plugin): 4.3.3
- WooCommerce: 6.9.4
- WP Rocket: 3.12.1
- Active Plugins: 11 (query-monitor AdminNotification CustomReports Funnels HeatmapSessionRecording MarketingCampaignsReporting SearchEngineKeywordsPerformance matomo-marketplace-for-$DB_USER matomo woocommerce wp-rocket)
- Warning Not compatible plugins: 1 (wp-rocket Matomo may work fine when using these plugins but there may be some issues. For more information see https://matomo.org/faq/$DB_USER/which-plugins-is-matomo-for-$DB_USER-known-to-be-not-compatible-with/ WP-Rocket is incompatible from version 3.12. Until fixes, please reinstall version 3.11.5 if you have a newer version. For more information please visit https://github.com/matomo-org/matomo-for-$DB_USER/wiki/Downgrade-wp-rocket-to-a-version-compatible-with-the-Matomo-plugin)
- Theme: twentytwentytwo (twentytwentytwo)
Server
- Server Info: Apache/2.4.41 (Ubuntu)
- PHP OS: Linux
- PHP Version: 8.0.22
- PHP SAPI: apache2handler
- PHP Error Reporting: 4437 After bootstrap: 4437
- PHP Found Binary: php -q
- Timezone: UTC
- WP timezone: +00:00
- 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: 40M
- WP Max Memory Limit: 512M
- Timezone version: 0.system
- Time: 1664326225
- Max Execution Time: 600
- Max Post Size: 8M
- Max Upload Size: 2097152
- Max Input Vars: 1000
- Disabled PHP functions: Yes (pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare,)
- zlib.output_compression is off: Yes
- Curl Version: 7.68.0, OpenSSL/1.1.1f
- Suhosin installed: No
Database
- MySQL Version: 8.0.30
- 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: 133
- DB tables exist: Yes
- Matomo users found: 1
- Matomo sites found: 1
- Required permissions: OK
Browser
- Browser: (Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0)
- Language: en-gb,en
`
Let me know if you need additional detail.
Sorry, made a mistake: Initially created this bug in a wrong repository https://github.com/matomo-org/plugin-Migration/issues/43
@AltamashShaikh Unless you have objections, I'm just adding this to the list of issues to be prioritised.
@mattmary I tried replicating the above issue
- Created 1 visit with above mentioned campaign and placement
http://localhost.demo.com/?mtm_campaign=2022_grundrauschen_dresden&mtm_placement=google#/Verf%C3%BCgbarkeitspr%C3%BCfung
- Checked Visits Log for today and I can see the above visit with campaign and placement
- Also tried creating a new segment as described and did a test
All seems to be working for me as expected, can you check if the visits log shows correct placement and campaign without any segment ?
Hello @AltamashShaikh When I've been able to reproduce this bug, I was in the WordPress plugin, not in Matomo: I had only the campaign parameter in the visitor log.
@mattmary Ill check if its specific to WP
@mattmary This seems to work in Wordpress too for me
Request URL 'http://localhost.testwordpress.com/?mtm_campaign=2022_grundrauschen_dresden'
Data in Matomo
Hello @AltamashShaikh
Sorry, but I can reproduce it: Here's what I get when I request https://wordpress.local/5.8/?mtm_campaign=2022_grundrauschen_dresden
here's my system report:
` # Matomo
- Matomo Plugin Version: 4.12.0
- Config exists and is writable.: Yes ("$abs_path/wp-content/uploads/matomo/config/config.ini.php" )
- JS Tracker exists and is writable.: Yes ("$abs_path/wp-content/uploads/matomo/matomo.js" )
- Plugin directories: Yes ([{"pluginsPathAbsolute":"$abs_path/wp-content/plugins/matomo/plugins","webrootDirRelativeToMatomo":"../"},{"pluginsPathAbsolute":"$abs_path/wp-content/plugins","webrootDirRelativeToMatomo":"../../"}])
- Tmp directory writable: Yes ($abs_path/wp-content/cache/matomo)
- Matomo Version: 4.12.0
- Matomo Blog idSite: 1
- Matomo Install Version: 4.6.0 (Install date: 2022-04-20 10:19:01)
- Upgrades outstanding: No
- Upgrade in progress: No
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: 2022-10-17 02:17:22
- Blog time: 2022-10-17 02:17:22 (Below dates are shown in blog timezone)
- Sync users & sites: Next run: 2022-10-17 10:21:10 (8 hours 3 min) ( Last started: 2022-10-16 19:03:42 (-7 hours 13 min). Last ended: 2022-10-16 19:03:42 (-7 hours 13 min). Interval: daily)
- Archive: Next run: 2022-10-17 02:19:05 (1 min 43s) ( Last started: 2022-10-17 02:12:17 (-5 min 5s). Last ended: 2022-10-17 02:12:17 (-5 min 5s). Interval: hourly)
- Update GeoIP DB: Next run: 2022-10-17 10:21:10 (8 hours 3 min) ( Last started: 2022-09-18 21:11:20 (-28 days 5 hours). Last ended: 2022-09-18 21:11:25 (-28 days 5 hours). Interval: matomo_monthly)
Mandatory checks
- PHP version >= : 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
- PageSpeed is turned off: ok
- GD > 2.x + FreeType (graphics): ok
- Other extensions: ok
- Other functions: ok
- Filesystem: ok
- Last Successful Archiving Completion: ok
- Database abilities: ok
- Max Packet Size: ok
- Geolocation: ok
- Update over HTTPS: ok
- Warning Heatmap & Session Recording Tracking: warning (Requesting '$site_url/wp-content/plugins/matomo/app/../../HeatmapSessionRecording/configs.php?idsite=1&trackerid=5lX6EM&url=http%3A%2F%2Ftest.test%2F' resulted in an SSL error. Maybe you are using a self signed certificate? Please open the URL manually in a browser to see if the response contains 'Piwik.HeatmapSessionRecording'. If not, you might need to modify your server configuration as this file needs to be accessible via a browser from the Internet or Intranet. )
- Supports Async Archiving: No
- Location provider ID: geoip2php
- Location provider available: Yes
- Location provider working: Yes
- Had visit in last 5 days: Yes
- Matomo URL: Yes ($site_url/wp-content/plugins/matomo/app/)
Matomo Settings
- Track mode: default
- Track codeposition: footer
- Track api endpoint: default
- Track js endpoint: default
- Version history: 4.12.0, 4.11.0, 4.10.0, 4.9.0, 4.6.0
- Core version: 4.12.0
- Last tracking settings update: 1650450019
- Last settings update: 1664481656
- Mail history: 2022-10-03 18:35:36, 2022-09-26 19:04:47, 2022-09-21 20:41:02
Logs
- ajax_tracker: 2022-10-12 19:08:30 (cURL error 60: SSL: no alternative certificate subject name matches target host name '$DB_USER.local' => AjaxTracker.php:91; MatomoTracker.php:844; Base.php:103; Woocommerce.php:176; Woocommerce.php:103; class-wp-hook.php:305; class-wp-hook.php:331; plugin.php:476; class-wc-cart.php:1276; class-wc-ajax.php:434; class-wp-hook.php:307; class-wp-hook.php:331; plugin.php:476; class-wc-ajax.php:93; class-wp-hook.php:307; class-wp-hook.php:331; plugin.php:476; template-loader.php:13; wp-blog-header.php:19; index.php:17;)
WordPress
- Home URL: $site_url
- Site URL: $site_url
- WordPress Version: 6.0.2
- Number of blogs: 1
- Multisite Enabled: No
- Network Enabled: No
- WP_DEBUG: Yes
- WP_DEBUG_DISPLAY: Yes
- WP_DEBUG_LOG: /tmp/wp.log
- DISABLE_WP_CRON: -
- FORCE_SSL_ADMIN: Yes
- WP_CACHE: No
- CONCATENATE_SCRIPTS: -
- COMPRESS_SCRIPTS: -
- COMPRESS_CSS: -
- ENFORCE_GZIP: -
- WP_LOCAL_DEV: -
- WP_CONTENT_URL: $site_url/wp-content
- WP_CONTENT_DIR: $abs_path/wp-content
- UPLOADS: -
- BLOGUPLOADDIR: -
- DIEONDBERROR: -
- WPLANG: -
- ALTERNATE_WP_CRON: -
- WP_CRON_LOCK_TIMEOUT: 60
- WP_DISABLE_FATAL_ERROR_HANDLER: -
- MATOMO_SUPPORT_ASYNC_ARCHIVING: No
- MATOMO_TRIGGER_BROWSER_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%/%postname%/
- Possibly uses symlink: No
- Upload base url: $site_url/wp-content/uploads
- Upload base dir: $abs_path/wp-content/uploads
- Upload url: $site_url/wp-content/uploads/2022/10
- Custom upload_path:
- Custom upload_url_path:
- Compatible content directory: Yes
WordPress Plugins
- Admin Notification (Matomo Plugin): 4.0.0
- Bandwidth (Matomo Plugin): 4.0.2
- Custom Reports (Matomo Plugin): 4.0.15
- Funnels (Matomo Plugin): 4.0.7
- Heatmap & Session Recording for Matomo: 4.5.0
- Marketing Campaigns Reporting (Matomo Plugin): 4.1.3
- Matomo Analytics - Ethical Stats. Powerful Insights.: 4.12.0
- Matomo Marketplace for WordPress: 1.0.11
- Migration (Matomo Plugin): 4.0.2
- Query Monitor: 3.10.1
- Search Engine Keywords Performance (Matomo Plugin): 4.3.3
- WooCommerce: 7.0.0
- Active Plugins: 12 (query-monitor AdminNotification Bandwidth CustomReports Funnels HeatmapSessionRecording MarketingCampaignsReporting Migration SearchEngineKeywordsPerformance matomo-marketplace-for-$DB_USER matomo woocommerce)
- Theme: twentytwentytwo (twentytwentytwo)
Server
- Server Info: Apache/2.4.41 (Ubuntu)
- PHP OS: Linux
- PHP Version: 8.0.23
- PHP SAPI: apache2handler
- PHP Error Reporting: 4437 After bootstrap: 4437
- PHP Found Binary: php -q
- Timezone: UTC
- WP timezone: +00:00
- 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: 40M
- WP Max Memory Limit: 512M
- Timezone version: 0.system
- Time: 1665973042
- Max Execution Time: 600
- Max Post Size: 8M
- Max Upload Size: 2097152
- Max Input Vars: 1000
- Disabled PHP functions: Yes (pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare,)
- zlib.output_compression is off: Yes
- Curl Version: 7.68.0, OpenSSL/1.1.1f
- Suhosin installed: No
Database
- MySQL Version: 8.0.30
- 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: 135
- DB tables exist: Yes
- Matomo users found: 1
- Matomo sites found: 1
- Required permissions: OK
Browser
- Browser: (Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:105.0) Gecko/20100101 Firefox/105.0)
- Language: en-gb,en
`
This might be related to L3-362