Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter marsronny

    (@marsronny)

    @dizzyatinnocraft I only use a small amount of (popular) plugins and the log looks fine to me.

    btw. There is someone who was able to confirm the same issue: https://forum.matomo.org/t/campaign-tracking-not-working-matomo-5-1-wp-6-5-5/58672 (I started the thread and someone confirmed the same problem)

    Of course here you go:

    				  # Matomo

    * Matomo-Plugin-Version: 5.1.1
    * Config existiert und ist schreibbar.: Ja ("$abs_path/wp-content/uploads/matomo/config/config.ini.php" )
    * JS Tracker existiert und ist schreibbar.: Ja ("$abs_path/wp-content/uploads/matomo/matomo.js" )
    * Plugin-Verzeichnisse: Yes ([{"pluginsPathAbsolute":"$abs_path\/wp-content\/plugins\/matomo\/plugins","webrootDirRelativeToMatomo":"..\/plugins"},{"pluginsPathAbsolute":"$abs_path\/wp-content\/plugins","webrootDirRelativeToMatomo":"..\/..\/"}])
    * Tmp-Verzeichnis schreibbar: Yes ($abs_path/wp-content/cache/matomo)
    * Matomo-Version: 5.1.0
    * Matomo Blog idSite: 1
    * Installierte Matomo-Version: 4.15.0 (Install date: 2023-08-13 21:36: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-Zeit: 2024-07-16 07:15:47
    * Blog-Zeit: 2024-07-16 09:15:47 (Die nachfolgenden Daten werden in der Blog-Zeitzone angezeigt)
    * Sync users & sites: Next run: 2024-07-16 21:37:01 (12 Stunden 21 Minuten) ( Last started: 2024-07-15 21:37:19 (-11 Stunden 38 Minuten). Last ended: 2024-07-15 21:37:19 (-11 Stunden 38 Minuten). Interval: daily)
    * Archive: Next run: 2024-07-16 09:36:04 (20 Minuten 17s) ( Last started: 2024-07-16 08:38:48 (-36 Minuten 59s). Last ended: 2024-07-16 08:38:51 (-36 Minuten 56s). Interval: hourly)
    * Update GeoIP DB: Next run: 2024-08-07 21:37:01 (22 Tage 12 Stunden) ( Last started: 2024-07-08 21:37:29 (-7 Tage 11 Stunden). Last ended: 2024-07-08 21:37:31 (-7 Tage 11 Stunden). Interval: matomo_monthly)

    ## Vorgeschriebene Prüfungen

    * PHP-Version >= 7.2.5: 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

    ## Optionale Prüfungen

    * 64-bit PHP Binär: ok
    * Tracker-Status: ok
    * Speicherlimit: ok
    * Zeitzone: ok
    * Öffnen einer URL: ok
    * GD > 2.x + FreeType (Grafiken): ok
    * Andere Erweiterungen: ok
    * Andere Funktionen: ok
    * Dateisystem: ok
    * Letzter erfolgreicher Abschluss der Archivierung: ok
    * Datenbankfähigkeiten: ok
    * Warning Maximale Packetgröße: warning (Es wird empfohlen die '<a href="https://dev.mysql.com/doc/refman/en/packet-too-large.html" rel="noreferrer noopener" target="_blank">max_allowed_packet</a>' Größe in Ihrer MySQL Datenbank auf mindestens 64MB zu erhöhen. Aktuell ist 16MB eingestellt. )
    * Standorterkennung: ok
    * Update über 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
    * Had visit in last 5 days: Yes
    * Matomo URL: Yes ($site_url/wp-content/plugins/matomo/app)

    ## Matomo Settings

    * Track mode: default
    * Track ecommerce: Yes
    * Track codeposition: footer
    * Track api endpoint: default
    * Track js endpoint: default
    * Version history: 5.1.1, 5.1.0, 5.0.8, 5.0.6, 5.0.5
    * Core version: 5.1.0
    * Last tracking settings update: 1696345861
    * Last settings update: 1708026388
    * Show get started page: 0
    * Track content: visible
    * Disable cookies: Yes

    ## Logs

    * Keine:

    # WordPress

    * Home URL: $site_url
    * Site URL: $site_url
    * WordPress Version: 6.5.5
    * 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: No
    * 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: -
    * 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: /%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/2024/07
    * Custom upload_path:
    * Custom upload_url_path:
    * Compatible content directory: Yes
    * WP_Filesystem Initialized: Yes

    # WordPress Plugins

    * Complianz | GDPR/CCPA Cookie Consent: 7.1.0
    * Divi Pixel: 2.29.4
    * Duplicate Page: 4.5.3
    * eRecht24 legal texts for WordPress: 3.3.11
    * Marketing Campaigns Reporting (Matomo Plugin): 5.0.4
    * Matomo Analytics - Ethical Stats. Powerful Insights.: 5.1.1
    * The SEO Framework: 5.0.6
    * WP-Optimize - Clean, Compress, Cache: 3.4.2
    * WPvivid Backup Plugin: 0.9.103
    * Active Plugins: 9 (MarketingCampaignsReporting:5.0.4 autodescription:5.0.6 complianz-gdpr:7.1.0 divi-pixel:2.29.4 duplicate-page:4.5.3 erecht24-2:3.3.11 matomo:5.1.1 wp-optimize:3.4.2 wpvivid-backuprestore:0.9.103)
    * Theme: Divi (divi-child)

    # Server

    * Server Info: Apache
    * PHP OS: Linux
    * PHP Version: 8.3.8
    * PHP SAPI: cgi-fcgi
    * PHP Binary Name: /usr/local/php83/bin/php-cgi
    * PHP Maxmind DB extension: Not loaded
    * PHP Error Reporting: 4437 After bootstrap: 4437
    * PHP Found Binary: /usr/bin/php -q
    * Timezone: UTC
    * WP timezone: Europe/Berlin
    * Locale: de_DE
    * User Locale: de_DE
    * 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: 2024.1
    * Time: 1721114149
    * Max Execution Time: 180
    * Max Post Size: 128M
    * Max Upload Size: 134217728
    * Max Input Vars: 4000
    * 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,)
    * zlib.output_compression is off: Yes
    * Curl Version: 7.64.0, OpenSSL/1.1.1n
    * Suhosin installed: No

    # PHP cli

    * PHP CLI Version: 7.3.31-1~deb10u7 (The detected PHP CLI version does not match the PHP web version. To avoid archiving errors, <a href="$site_url/wp-admin/admin.php?page=matomo-settings&tab=advanced#matomo[disable_async_archiving]">enable archiving via HTTP requests</a>, or <a href="https://matomo.org/faq/how-to-solve-the-error-message-your-php-cli-version-is-not-compatible-with-the-matomo-requirements/" target="_blank" rel="noreferrer noopener">manually set the path to your PHP CLI executable</a> to the one for PHP version 8.3.8.)
    * MySQLi support: ok

    # Database

    * MySQL Version: 8.0.33
    * Mysqli Connect: Yes
    * Force MySQL over Mysqli: No
    * DB Prefix: dR43plCpi_
    * DB CHARSET: utf8
    * DB COLLATE:
    * SHOW ERRORS: No
    * SUPPRESS ERRORS: No
    * Uses Socket: No
    * Uses IPv6: No
    * Matomo tables found: 140
    * DB tables exist: Yes
    * Matomo users found: 3
    * Matomo sites found: 1
    * Erforderliche Berechtigungen: OK

    # Browser

    * Browser: (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36)
    * Language: de,en,es
    Thread Starter marsronny

    (@marsronny)

    Of course!

    • Is there data available in other reports, or is it just the campaign reports that are missing data?
      • All the other reports are working without any problems. It’s just the campaign reports.
    • Is there data in the Visits Log?
      • Yes. All good here.
    • If there is, do you see any visits that have come from a campaign there?
      • Nothing. I’ve checked various days on the visitors log. Can’t see any link to a campaign.
    Thread Starter marsronny

    (@marsronny)

    No. As I’ve already mentioned I uninstalled the plugin because I don’t like it. Now it seems that you blocked the native WordPress update settings because I can’t toggle automatic plugin updates anymore. How can I return to the original state where I can toggle automatic updates in WordPress without the plugin like it used to work before?

    Thread Starter marsronny

    (@marsronny)

    Thread Starter marsronny

    (@marsronny)

    Hello Rogier,

    Unfortunately the issue still persists. I didn’t change the configuration and I didn’t add any plugins or third party services. I just updated the plugin Complianz. Before the update it showed the Cookie Banner and after the update it doesn’t show the banner. The issue isn’t resolved.

    I have several websites where the cookiebanner is not showing anymore after updating to new 7 version.
    Deleting old cookies does not solve the problem, even incognitomode

    I can confirm that. I’m on V7.0.2

    Thread Starter marsronny

    (@marsronny)

    When is the next release scheduled?

    I got the same issue on my clients website after updating to version 3.6.2.

    I did a fallback to version 3.6.1 and everything works just fine.

    Looking forward to your fix!

Viewing 8 replies - 1 through 8 (of 8 total)