Thomas
Forum Replies Created
-
Great @mohammedsh thanks for letting us know
Thanks for reporting this @amedat and sorry about this.
It seems there is an error in the
w3-total-cacheplugin which is causing issues for our plugin:> Call to undefined function mysql_connect() in $ABSPATH/wp-includes/wp-db.php:1688 Stack trace: #0 $ABSPATH/wp-content/plugins/w3-total-cache/DbCache_WpdbNew.php(97): wpdb->db_connect()
Is there maybe an update available for W3 Total Cache or is there any chance you could reach out to them regarding this error?
Hi @mohammedsh sorry you ran into these issues. Is the plugin still installed now? If so, could you enable maybe the
safe modeas described in https://matomo.org/faq/wordpress/how-do-i-find-and-copy-the-system-report-in-matomo-for-wordpress/ and send us the system report?Basically, by adding
define( 'MATOMO_SAFE_MODE', true );to your wp-config.php it should be possible to see the system report and then it should likely also be possible to deactivate the plugin if needed.Does this help @mohammedsh ?
No problem at all @picxel Let us know if we can be of any help in the future.
Hi @picxel thanks for creating this issue and sorry for the trouble. I just checked out your website but the tracking code is currently not embedded. I assume you have the tracking disabled currently?
Usually, when using Matomo for WordPress, your idSite should be pretty much always
1. Is there any chance you are using Matomo On-Premise or Matomo Cloud? In this case you would need to use this plugin: https://wordpress.org/plugins/wp-piwik/If you don’t have a standalone Matomo install, could you post your system report (should be anonymised automatically)? see
https://matomo.org/faq/wordpress/how-do-i-find-and-copy-the-system-report-in-matomo-for-wordpress/Thanks for this @r1baum very appreciated and we will certainly consider the DB schema check
Thanks for this @yhsh and be great to comment here if you run into this issue again and we’ll follow up.
Hi @r1baum thanks for creating this issue and sorry about the trouble. I can’t explain yet why it would differ so much except if the update maybe ran twice in which case the messages you’re seeing would be likely expected and could be ignored. Our update scripts are written so they can be executed multiple times and even if the correctly expected table structure already exists it simply skips a change because it was already executed. It is possible that WordPress maybe still shows these warnings when this happens since their DB connector sometimes simply shows any error message depending on the WordPress configuration. We’re trying to suppress these messages when this happens, but maybe there’s some config that enforces these messages to be shown anyway.
We do have an open/unresolved issue to verify the DB schema is correct in https://github.com/matomo-org/matomo/issues/11540 but it’s not implemented yet as while it seems this be something trivial it’s unfortunately not.
Can you check if Matomo is still tracking data? For example when you go to
* WP admin dashboard
* Matomo Analytics -> Reporting
* Click on “Visitors -> Visits log” and/or “Visitors -> Real time”Do you see any recent data in these reports? You might have to select for example today.
Looking at the error messages it seems all good to me and the update script was simply executed twice due to potentially a race condition.
Hi @yhsh thanks for creating this issue. Do I understand this correctly the plugin was updated correctly but the tracking got disabled?
Generally, there isn’t really any way AFAIK that disabling the tracking could be triggered by our plugin unless the plugin was uninstalled and then installed again. I’m not sure if this could have happened somehow during the update as it seems you’ve had issues there. Maybe when the update failed WordPress did uninstall the plugin because the files were missing. This would likely not be anything we could influence since it is all WordPress logic. It seems related though to the error you had.
> Could you pls send me in the right direction to correct this update error? Iām again guessing that I need to change some setting(s) in Matomo too?
Unfortunately I can’t help regarding any certificates as the origin server would be the WordPress plugin directory server and not a server from us. Looking at the screenshot you may want to get in touch with your hoster maybe or even with Cloudflare. I couldn’t find this error message in WordPress itself so I’m assuming Cloudflare might have triggered that error.
Thanks for this @markhowellsmead very appreciated.
We’ve created a patch that should fix this in https://github.com/matomo-org/matomo/pull/17295/files
Just in case you’re needing an immediate fix for this and are comfortable and familiar with editing PHP files from your WordPress directly, then will free to apply the changes from the above link to the file
wp-content/plugins/matomo/app/plugins/GeoIp2/GeoIP2AutoUpdater.php.Thanks again for reporting this and sorry for the inconvenience. This should be fixed as part of the next release.
Awesome, thanks for this @janaa we’ve already tweaked the wording to include clear and purge there to make it more clear and we’ll include this in the next release (which should be available soon) š
Thanks for this again
Hi @janaa
sorry that’s not worded clearly. We will change this and make it more clear. What’s meant here is that if you are using a caching plugin, say WP-Rocket, then it is recommended to go to the settings of that caching plugin and clear/reset/invalidate the cache. Not every caching plugin has such an option. If you’re not sure what to do, then likely you won’t have to do anything.
You don’t need to exclude anything specifically otherwise.
Does this maybe help?
Great to hear @leogc feel free to let us know how you go. We’re always happy about any kind of feedback (good or bad).
Glad you found it @denisit71 . Thanks for finding this out and reaching out to them. Very appreciated.
Thanks for this @denisit71
Any chance you could post your system report see https://matomo.org/faq/wordpress/how-do-i-find-and-copy-the-system-report-in-matomo-for-wordpress/ ? The report should be anonymised automatically. Alternatively, you could email this to wordpress@matomo.org .
These notices/warnings should all be suppressed and not shown. There is likely some PHP setting that forces these messages to show up. Maybe some plugin overwrites the error reporting level and the system report would hopefully help us reproduce this issue. Thanks for this.