awilmsmeier

Thanks for following up. I will try the update once it is available. Installing Matomo separately does not seem to make sense for me right now, given the number of visits and that we are re-launching our web site in a few weeks from now. But good to know that this is a better option with higher traffic volumes.

It’s a bit of a surprise that WordPress should take up so much time – shouldn’t that be the same for all requests to our site? Not just for requests to Matomo components? Haven’t seen that in GTMETRIX…

Thanks again …

Yes, of course.
We are hosting at https://www.hostpoint.ch, the package is “Smart Webhosting (inkl. SITES Limited)”
So far, performance has been reasonable and sufficient for our purposes.

Hi, See the system report below, hope this help
I’m OK to wait for the next release and re-test – let me know when this will be out…

—-
# Matomo

* Matomo Plugin Version: 1.1.2
* Config exists and is writable.: Yes (“$ABSPATH/wp-content/uploads/matomo/config/config.ini.php” )
* JS Tracker exists and is writable.: Yes (“$ABSPATH/wp-content/uploads/matomo/matomo.js” )
* Plugin directories: Yes ([{“pluginsPathAbsolute”:”$ABSPATH\/wp-content\/plugins\/matomo\/plugins”,”webrootDirRelativeToMatomo”:”..\/”}])
* Tmp directory writable: Yes ($ABSPATH/wp-content/cache/matomo)
* Matomo Version: 3.13.6
* Matomo Blog idSite: 1
* Matomo Install Version: 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: 2020-06-12 06:35:10
* Blog time: 2020-06-12 08:35:10 (Below dates are shown in blog timezone)
* Sync users & sites: Next run: 2020-06-12 13:29:46 (4?hours?54?min) ( Last started: 2020-06-11 13:30:58 (-19?hours?4?min). Last ended: 2020-06-11 13:30:58 (-19?hours?4?min). Interval: daily)
* Archive: Next run: 2020-06-12 09:29:46 (54?min?36s) ( Last started: 2020-06-12 08:31:37 (-3?min?33s). Last ended: 2020-06-12 08:31:40 (-3?min?30s). Interval: hourly)
* Update GeoIP DB: Next run: 2020-07-10 13:29:46 (28?days?4?hours) ( Last started: 2020-06-10 13:32:20 (-1?days?19?hours). Last ended: 2020-06-10 13:32:23 (-1?days?19?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

* Tracker status: ok
* Memory limit: ok
* Time zone: ok
* Open URL: ok
* PageSpeed disabled: ok
* GD > 2.x + Freetype (graphics): ok
* Other extensions: ok
* Other functions: ok
* Warning Filesystem: warning (Your server is using an NFS filesystem. This means Matomo will be extremely slow when using file based sessions. )
* Archive Cron: ok
* Last Successful Archiving Completion: ok
* Warning Max Packet Size: warning (It is recommended to configure a ‘max_allowed_packet’ size in your MySQL database of at least 64MB. Configured is currently 16MB. )
* Geolocation: ok
* Update over HTTPS: ok
* Writable JavaScript Tracker (“/matomo.js”): ok
* Supports Async Archiving: No
* Location provider ID: geoip2php
* Location provider available: Yes
* Location provider working: Yes
* Had visit in last 5 days: Yes

## Matomo Settings

* Track mode: default
* Track codeposition: footer
* Track api endpoint: default
* Track js endpoint: default
* Version history: 1.1.2, 1.1.1, 1.1.0, 1.0.6
* Core version: 3.13.6
* Last tracking settings update: 1591781437
* Last settings update: 1591781437
* Show get started page: 0
* Track search: Yes
* Track 404: Yes
* Track admin: Yes

## Logs

* None:

# WordPress

* Home URL: $site_url
* Site URL: $site_url
* WordPress Version: 5.4.2
* Number of blogs: 1
* Multisite Enabled: No
* Network Enabled: No
* WP_DEBUG: Yes
* WP_DEBUG_DISPLAY: No
* WP_DEBUG_LOG: Yes
* 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: –
* Permalink Structure: /%postname%/
* Possibly uses symlink: No
* Compatible content directory: Yes

# WordPress Plugins

## MU Plugins

* aaa-wp-cerber.php: 1.0

## Plugins

* Add-on WooCommerce MailPoet 3: 1.1.7
* Advanced Order Export For WooCommerce: 3.1.4
* Ajax Search Lite: 4.8.1
* Async JavaScript: 2.20.03.01
* Autoptimize: 2.7.3
* Breeze: 1.1.6 (Network enabled)
* Broken Link Checker: 1.11.13
* Cache Enabler: 1.3.5
* Duplicate Post: 3.2.4
* Duplicator: 1.3.34
* Easy HTTPS (SSL) Redirection: 1.9.1
* Email Address Encoder: 1.0.21
* Enable Media Replace: 3.4.0
* EventON: 2.8.5
* EventON – Event Lists Ext: 0.15
* EventON – Event Reviewer: 1.0.2
* EventON – Event Tickets: 1.7.10
* Event Tickets: 4.12.1.2
* Hummingbird: 2.4.2 (Network enabled)
* Image Cleanup: 1.9.2
* Juicer: 1.9.1
* Kadence Blocks – Gutenberg Page Builder Toolkit: 1.8.5
* Kadence Blocks Pro: 1.4.9
* Kadence Custom Fonts: 1.0.3
* Kadence WooCommerce Email Designer: 1.4.1
* Kadence WooCommerce Extras: 1.6.9
* MailPoet 3 (New): 3.47.4
* Maps Block for Gutenberg: 1.30
* Matomo Analytics – Ethical Stats. Powerful Insights.: 1.1.2
* Media Cleaner: 5.6.3
* Modern Events Calendar Lite: 5.6.0
* Rate my Post – WP Rating System: 3.2.1
* Search Regex: 2.1
* ShortPixel Image Optimizer: 4.19.2
* Site Reviews: 4.6.3
* Slimstat Analytics: 4.8.8.1
* SmartCrawl: 2.6.1 (Network enabled)
* Swift Performance Lite: 2.1.3
* The Events Calendar: 5.1.2.1
* The SEO Framework: 4.0.7
* Ultimate Addons for Gutenberg: 1.15.2
* UpdraftPlus – Backup/Restore: 1.16.25
* W3 Total Cache: 0.14.1 (Network enabled)
* WooCommerce: 4.2.0
* WooCommerce Multilingual: 4.9.0
* WooCommerce PDF Invoices & Packing Slips: 2.5.1
* WooCommerce Stripe Gateway: 4.4.0
* WOOF – WooCommerce Products Filter: 1.2.4
* WP-DBManager: 2.80.3
* WP-PostRatings: 1.88
* WP All Import: 3.5.3
* WP Cerber Security, Antispam & Malware Scan: 8.6.5 (Network enabled)
* WPML All Import: 2.1.1
* WPML Media: 2.5.5
* WPML Multilingual CMS: 4.3.15
* WPML String Translation: 3.0.11
* WPML Support Toolbox: 1.0.5
* WPML Translation Management: 2.9.8
* WP Statistics: 12.6.13
* WP Super Cache: 1.7.1
* WP User Avatar: 2.2.6
* XCloner – Site Backup and Restore: 4.2.0
* Active Plugins: 39 (sitepress-multilingual-cms add-on-woocommerce-mailpoet ajax-search-lite async-javascript autodescription autoptimize broken-link-checker cache-enabler duplicate-post duplicator email-address-encoder enable-media-replace event-tickets https-redirection kadence-blocks-pro kadence-blocks kadence-woocommerce-email-designer mailpoet map-block-gutenberg matomo search-regex the-events-calendar ultimate-addons-for-gutenberg updraftplus woo-order-export-lite woocommerce-gateway-stripe woocommerce-multilingual woocommerce-pdf-invoices-packing-slips woocommerce-products-filter woocommerce wp-all-import wp-cerber wp-user-avatar wpml-all-import wpml-media-translation wpml-string-translation wpml-support-toolbox wpml-translation-management xcloner-backup-and-restore)

# Server

* Server Info: Apache
* PHP OS: FreeBSD
* PHP Version: 7.3.18
* PHP SAPI: cgi-fcgi
* PHP Binary Name: php-cgi
* PHP Found Binary: php -q
* Timezone: UTC
* WP timezone: Europe/Zurich
* Locale: en_US
* User Locale: en_US
* Memory Limit: 256M (At least 128MB recommended. Depending on your traffic 256MB or more may be needed.)
* WP Memory Limit: 256M
* WP Max Memory Limit: 256M
* Time: 1591943711
* Max Execution Time: 30
* Max Post Size: 16M
* Max Upload Size: 16777216
* Max Input Vars: 1000
* Disabled PHP functions: No
* zlib.output_compression is off: Yes
* Curl Version: 7.70.0, OpenSSL/1.1.1g
* Suhosin installed: No

# Database

* MySQL Version: 5.5.5
* 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: 281
* Matomo users found: 3
* Matomo sites found: 1
* Required permissions: OK

# Browser

* Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_5) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.1 Safari/605.1.15
* Language: de-ch

Great, looking forward to having that feature in Matomo.
Would those widgets (with the saved settings) become available in the WordPress Admin Dashboard as well?

Hi,
Thanks, that works – looking forward to the full version (e.g. with some graphical representations and comparison to previous periods)…
Best regards,
Andreas

PS: In the Matomo Dashbaord – is there a way to save filters and comparison flags? Seems like saving the dashboard does not save those settings? I’d like to always see current month vs. previous month when I enter the Matomo dashboard.
(Not a showstopper, of course, just convenience)

Hi,
that is helpful for now. I’m only starting with Matomo so I can wait for the final version to become available.
Thanks for your quick response.
Andreas

Sorry, was on vacation, the issue is still there, but in my test, I have been unable to reproduce (other than the attribute where the error occurs). So from my experience as a developer, debugging would be the way to go. Happy to support with that or with more targeted testing. Let me know how to proceed from here.
Best regards,
Andreas

Hin,
Thanks for the reply. I have changed the width to 300 as suggested. It looks a lot better now, but the images don’t adjust to the window size.

On a large screen it looks OK, on a smaller screen the image are cut off on the right. It’s OK for now, but would be good to find a real fix?
Thanks,
Andreas

Thanks,
Looks like this is a Gutenberg limitation at this point.
I was aware of the option to change the image width…
Thanks,
Andreas

Hi,
The issue is still there…
– it works for all other attributes
– it works when I create the same attribute value with an “_” (as expected)
– it does not work when I just use the same selection on a different page
– it does work when I create a new attribute with the same term

I can give you access to our sandbox site, if that helps?

In the meantime, I have reverted back to good old short codes – for two reasons:
1) this bug
2) there is no pagination is your Blocks – I had created a feature request, but for some reason you seem to have decided that you don’t want to offer that in blocks – is there a change you would reconsider that?
Best regards,
Andreas

Was a WPML issue – this is resolved now (WP 5.1 and WPML 4.2.2)

An updated version of the config file – for what it’s worth…
(this issue can be marked as resolved)

<gutenberg-block type=”kadence/spacer” translate=”0″></gutenberg-block>
<gutenberg-block type=”kadence/rowlayout” translate=”0″></gutenberg-block>
<gutenberg-block type=”kadence/column” translate=”0″></gutenberg-block>
<gutenberg-block type=”kadence/icon” translate=”1″>
<xpath>//div/a/@href</xpath>
</gutenberg-block>
<gutenberg-block type=”kadence/tab” translate=”0″></gutenberg-block>
<gutenberg-block type=”kadence/accordion” translate=”0″></gutenberg-block>
<gutenberg-block type=”kadence/advancedheading” translate=”1″>
<xpath>//div/h1</xpath>
<xpath>//div/h2</xpath>
<xpath>//div/h3</xpath>
<xpath>//div/h4</xpath>
<xpath>//div/h5</xpath>
<xpath>//div/h6</xpath>
</gutenberg-block>
<gutenberg-block type=”kadence/advancedbtn” translate=”1″>
<xpath>//div/a/span</xpath>
<xpath>//div/a/@href</xpath>
</gutenberg-block>
<gutenberg-block type=”kadence/tabs” translate=”1″>
<xpath>//a[@class=”kt-tab-title”]</xpath>
</gutenberg-block>
<gutenberg-block type=”kadence/infobox” translate=”1″>
<xpath>//div/h1</xpath>
<xpath>//div/h2</xpath>
<xpath>//div/h3</xpath>
<xpath>//div/h4</xpath>
<xpath>//div/h5</xpath>
<xpath>//div/h6</xpath>
<xpath>//div/p</xpath>
<xpath>//div/a/@href</xpath>
</gutenberg-block>
<gutenberg-block type=”kadence/pane” translate=”1″>
<xpath>//span[@class=”kt-blocks-accordion-title”]</xpath>
</gutenberg-block>

+1

I’d be interested in that, too…

Hi,
Good news, WPML has finally fixed the error in their 4.2.2 version – works for me in combination with WP 5.1. I consider the issue resolved…

To make translation more convenient, you may want to provide a WPML-config.xml – I’ve given it a stab and that works for me – see below for details:

<gutenberg-block type=”kadence/spacer” translate=”0″></gutenberg-block>
<gutenberg-block type=”kadence/rowlayout” translate=”0″></gutenberg-block>
<gutenberg-block type=”kadence/column” translate=”0″></gutenberg-block>
<gutenberg-block type=”kadence/icon” translate=”0″></gutenberg-block>
<gutenberg-block type=”kadence/tab” translate=”0″></gutenberg-block>
<gutenberg-block type=”kadence/accordion” translate=”0″></gutenberg-block>
<gutenberg-block type=”kadence/advancedheading” translate=”1″>
<xpath>//div/h1</xpath>
<xpath>//div/h2</xpath>
<xpath>//div/h3</xpath>
<xpath>//div/h4</xpath>
<xpath>//div/h5</xpath>
<xpath>//div/h6</xpath>
</gutenberg-block>
<gutenberg-block type=”kadence/advancedbtn” translate=”1″>
<xpath>//div/a/span</xpath>
</gutenberg-block>
<gutenberg-block type=”kadence/tabs” translate=”1″>
<xpath>//li/a/span</xpath>
</gutenberg-block>
<gutenberg-block type=”kadence/infobox” translate=”1″>
<xpath>//div/h1</xpath>
<xpath>//div/h2</xpath>
<xpath>//div/h3</xpath>
<xpath>//div/h4</xpath>
<xpath>//div/h5</xpath>
<xpath>//div/h6</xpath>
<xpath>//div/p</xpath>
</gutenberg-block>
<gutenberg-block type=”kadence/pane” translate=”1″>
<xpath>//button/div/span</xpath>
</gutenberg-block>

Thanks for the support.