chrisstanyon

Seriously !! Your solution is a 2-year old PR that ‘should’ be deployed in the next release. A PR that assumes I have the source code and not the production ready minified scripts.

FYI – I’ve just updated the Plugin and it looks like it still hasn’t been fixed.

There must be a straight-forward way to get Tag Manager and WooCommerce tracking working at the same time. I can’t be the first person to want this

Hi,

The only ecommerce plugin installed is WooCommerce, and I can confirm that ecommerce tracking is enabled in the Matomo Settings.

I thought I was already reaching out to your support by posting here, although so far, there hasn’t really been any support – just basic questions. No-one has attempted to even address my original question !!! Your plugin tracks e-commerce events when Default Tracking is enabled – but it doesn’t track e-commerce events if Tag Manager is enabled. I just want to know why !

Sure – here you go:

Matomo

• Matomo Plugin Version: 4.13.3
• 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”:”..\/”}])
• Tmp directory writable: Yes ($abs_path/wp-content/cache/matomo)
• Matomo Version: 4.13.3
• Matomo Blog idSite: 1
• Matomo Install Version: 4.13.3 (Install date: 2023-02-10 14:28:50)
• 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: 2023-02-27 09:26:35
• Blog time: 2023-02-27 09:26:35 (Below dates are shown in blog timezone)
• Sync users & sites: Next run: 2023-02-27 14:32:39 (5 hours 6 min) ( Last started: 2023-02-26 15:02:05 (-18 hours 24 min). Last ended: 2023-02-26 15:02:06 (-18 hours 24 min). Interval: daily)
• Archive: Next run: 2023-02-27 09:28:54 (2 min 18s) ( Last started: 2023-02-27 08:32:02 (-54 min 34s). Last ended: 2023-02-27 08:32:04 (-54 min 32s). Interval: hourly)
• Update GeoIP DB: Next run: 2023-03-12 14:32:40 (13 days 5 hours) ( Last started: 2023-02-10 15:02:03 (-16 days 18 hours). Last ended: 2023-02-10 15:02:13 (-16 days 18 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
• Database abilities: ok
• Max Packet Size: ok
• Geolocation: ok
• Update over HTTPS: ok
• Supports Async Archiving: Yes
• Location provider ID: geoip2php
• Location provider available: Yes
• Location provider working: Yes
• Matomo URL: Yes (xxxxxxxxxxxxxx/wp-content/plugins/matomo/app)

Matomo Settings

• Track mode: default
• Track codeposition: footer
• Track api endpoint: default
• Track js endpoint: default
• Version history: 4.13.3
• Core version: 4.13.3
• Last tracking settings update: 1676307594
• Last settings update: 1676307594
• Show get started page: 0

Logs

• None:

WordPress

• Home URL: $site_url
• Site URL: $site_url
• WordPress Version: 6.1.1
• Number of blogs: 1
• Multisite Enabled: No
• Network Enabled: No
• WP_DEBUG: No
• WP_DEBUG_DISPLAY: No
• WP_DEBUG_LOG: No
• DISABLE_WP_CRON: Yes
• 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: –
• 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: /%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/2023/02
• Custom upload_path:
• Custom upload_url_path:
• Compatible content directory: Yes

WordPress Plugins

• Elementor: 3.11.1
• Elementor Pro: 3.11.1
• LiteSpeed Cache: 5.3.2
• Matomo Analytics – Ethical Stats. Powerful Insights.: 4.13.3
• UpdraftPlus – Backup/Restore: 1.22.24
• WooCommerce: 7.4.0
• WooCommerce Stripe Gateway: 7.1.0
• WP Mail SMTP: 3.7.0
• Active Plugins: 7 (elementor-pro elementor matomo updraftplus woocommerce-gateway-stripe woocommerce wp-mail-smtp)
• Theme: hello-elementor (hello-theme-child)

Server

• Server Info: LiteSpeed
• PHP OS: Linux
• PHP Version: 7.4.29
• PHP SAPI: litespeed
• PHP Binary Name: lsphp
• PHP Maxmind DB extension: Not loaded
• PHP Error Reporting: 0 After bootstrap: 0
• PHP Found Binary: php -q
• Timezone: UTC
• WP timezone: +00:00
• Locale: en_GB
• User Locale: en_GB
• Memory Limit: 2G (At least 128MB recommended. Depending on your traffic 256MB or more may be needed.)
• WP Memory Limit: 40M
• WP Max Memory Limit: 2G
• Timezone version: 2022.1
• Time: 1677489998
• Max Execution Time: 30
• Max Post Size: 8M
• Max Upload Size: 8388608
• Max Input Vars: 1000
• Disabled PHP functions: No
• zlib.output_compression is off: Yes
• Curl Version: 7.84.0, OpenSSL/1.1.1d
• Suhosin installed: No

PHP cli

• PHP cli Version: 7.4.29
• MySQLi support: ok

Database

• MySQL Version: 10.2.32
• Mysqli Connect: Yes
• Force MySQL over Mysqli: No
• DB Prefix: Ia05j_
• DB CHARSET: utf8
• DB COLLATE:
• SHOW ERRORS: No
• SUPPRESS ERRORS: No
• Uses Socket: No
• Uses IPv6: No
• Matomo tables found: 97
• DB tables exist: Yes
• Matomo users found: 2
• Matomo sites found: 1
• Required permissions: OK

Browser

• Browser: (Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/110.0)
• Language: en-gb,en

Hi,

No – I’m NOT using MultiSite. This is a simple, basic, single site installation.

Yep – same problems – been having it for a while now, with different versions. Currently running Pro 3.3.0 (default language). WordPress just will not accept that the Translation Update has been done – keeps showing as requiring Update.

@lavig1 – is this likey to be addressed as a bug any time soon.

Hey Peter,

Just a quick update – I figured out the issue with the MySQL ND Driver (get_result() error). Fixed that and dropped the WFWAF_STORAGE_ENGINE constant back in. No more errors, but it’s still not showing as Optimized ??

Hi Peter,

No worries. Appreciate you taking the time help.

OK. The current setup is that WordPress is only installed on a subdomain (shop.chrisstanyon.com). The folder for this subdomain is a sub-folder of my home folder, so the full path to the subdomains document root is:

/var/www/vhosts/chrisstanyon.com/shop.chrisstanyon.com

There are no other WP installations running on this particular hosting package.

I replaced the wordfence-waf.php code with your code (prior to this it had the full path, rather than __DIR__) and it broke the site. Looked at the error logs, and setting the STORAGE_ENGINE to mysqli causes a problem. The full error was:

PHP Fatal error: Uncaught Error: Call to undefined method mysqli_stmt::get_result() in /var/www/vhosts/chrisstanyon.com/shop.chrisstanyon.com/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/mysql.php:949

We do have the MySQL ND driver installed, so not sure why it can’t find get_result() – we’re running MariaDB, but not sure that would effect it !

Now here’s the thing that’s baffling me. The WordFence plugin IS calling the wordfence-waf.php file and consequently loading the waf/bootstrap.php file. If I add in some logging to both of these files, I can see those entries in the log file:

if (file_exists(__DIR__ . '/wp-content/plugins/wordfence/waf/bootstrap.php')) {
    define("WFWAF_LOG_PATH", __DIR__ . '/wp-content/wflogs/');
    error_log("The WAF Bootstrap file exists");
    include_once __DIR__ . '/wp-content/plugins/wordfence/waf/bootstrap.php';
}

I’ve added similar error_log calls to the bootstrap.php file, and I can also see them in the logs.

It seems that it’s correctly loading those files – it’s just that the plugin doesn’t appear to recognise that ?? Strange indeed.

Anyway, hope that helps, but if you want any more info, please do let me know.

Thanks

Chris

Haha – I did notice that and wondered whether it was a typo or some special format I was unaware of … so I tried it with the extra quote and it broke. I figured it was a typo and dropped it ??

Not sure whether this will help debug or not, but I’ve uploaded a phpinfo() page to the site: https://shop.chrisstanyon.com/pi.php

Thanks

Hey Peter,

Sadly, no change. The prepend entry is still showing in phpinfo(), and the bootstrap.php file is still firing, but the diagnostics tab STILL shows ‘WAF auto prepend active’ as No!

Thanks for the reply Peter,

I’ve already got the noabort rule in the htaccess file. I have no problem running scans.

The issue is that I can only get the Basic Protection working on the firewall (not the Extended Protection). Despite the wordpress-waf file being present in the root, phpinfo() showing the auto_prepend_file pointing correctly, and the bootstrap.php file actually firing, the diagnostics still show that ‘WAF auto prepend active’ is set to No – I would expect that to be set to Yes.

Just discovered exactly the same problem.

For me, it only seems to happen when I use the Buy Now button on a Single Product with Variations.

The emails that go out to the Customer, the order displayed in the backend, and the info shown on the PayPal site all include the genuine variation info (Colour: Blue for example), but it also shows the nonce, ppec-add-to-cart, quantity, product_id and variation_id as part of the Variation Data:

nonce: xxxxxxxx
Frame Type: None
Print Size: A3 (297 x 420 mm)
quantity: 1
ppec-add-to-cart: 216
product_id: 216
variation_id: 285

If I add the product to the Basket using the standard Add to Cart button, then it works fine, so it appears to be a problem with the PayPal button.

Only option I have at the moment is to disable PayPal for the Single Product pages.

WordPress and all plugins are up to date:

WordPress: 5.0.3
WooCommerce: 3.5.4
WooCommerce PayPal Checkout Gateway: 1.6.9

There does seem to be a bug report of this on GitHub – https://github.com/woocommerce/woocommerce-gateway-paypal-express-checkout/issues/498