dizzyatinnocraft

Hi @koobm, one more version to test if you are able to: https://github.com/matomo-org/matomo-for-wordpress/releases/download/5.1.7-b2/matomo.zip . After running the import there shouldn’t be any archiving errors. Thanks again for your help.

@newki75 If the rest of Matomo’s interface looks like it’s working you might be able to ignore that error (the zlib.output_compression one). We might be able to get rid of that diagnostic check altogether in the next version.

Hi @newki75, are you still experiencing this problem?

Now the log periodically shows errors from the cron run.

Ah, those errors point to another bug in the import (again, apologies). You’ll have to re-run the import with another pre-release that fixes this issue (this should be the last problem I think).

Unfortunately my SSH connection was lost and the process cancelled during the report generation phase (somewhere around 60-90 minutes in).

If the process was cut off, it would just get re-started by wp-cron eventually so there’s no issue there. It might be a good idea to run the import command through nohup next time if possible to make sure it keeps running even if your connection is lost.

Only some special reports (e.g. time of day; devices) look incomplete.

Would you be able to explain how they look incomplete? We can try and fix this in a future version.

Just out of curiosity, I found that in Matomo onPremise the report generation can be re-initiated. Is there also a way to do so in the WordPress version?

Triggering archiving manually can be done via the Troubleshooting tab in Diagnostics. But if you want to completely re-process reports, you’d need to invalidate the periods you want to re-process first. To do this, you can use the “Invalidate Reports” plugin (available through the Matomo Marketplace).

We’ll try and get a new pre-release up soon, thanks for giving your time to test this version, it’s very much appreciated!

I’ve looked at the stats in more detail for this website and I can see that there were between 0 and 10 visits registered per week during the interim period.

Can you confirm that those visits appear outside of the Visits Log in normal reports (eg, the summary page)?

This was a very sudden change and doesn’t tie in the number of form submissions we received from website visitors over the same period.

If archiving is working then I’m not sure what the discrepancy could be due to. Can you share the number of form submissions you are receiving compared to visits? How are you tracking form submissions?

Is it possible that users aren’t consenting to being tracked or have an adblocker in use or a combination of these two factors? If you can add whether a user consented to tracking to whatever mechanism you use to track form submissions you might be able to see if this is the case.

Hi @koobm, here is a pre-release with the import fixes: https://github.com/matomo-org/matomo-for-wordpress/releases/download/5.1.7-b1/matomo.zip . Does it solve the import problems for you?

Hi @markhowellsmead, you can see the list of releases here: https://github.com/matomo-org/matomo-for-wordpress/releases . From that list you should see there was no release in mid-August.

If visits are showing up in the real time visits reports but not in other reports, that means archiving isn’t running successfully. Do you see any error logs for archiving? If you run archiving manually via Matomo Analytics > Diagnostics > Troubleshooting, does data appear in the reports?

If visits are showing up only for you in an incognito window (as in, there are no visits in the real time reports and the visitor log except your visits), that’s a bit stranger and will require a closer look.

Hi @koobm, would you be willing to test a pre-release version of the plugin to ensure the importer will work for you?

Due to a lack of response, I’ll mark this as resolved. However, if you still need help or need help with something else, feel free to comment further.

Hi @newki75, can you check for a file at /path/to/wordpress/wp-content/uploads/matomo/config/config.ini.php ? If it exists, try deleting it and installing the plugin again.

@kinkmobile If you manually invoke archiving by clicking “Archive Reports” in “Matomo Analytics > Diagnostics > Troubleshooting” do you see the same error (you may have to look again in the Logs section of Diagnostics for a recent error)?

@koobm apologies for the continued inconvenience, we’ll try to take care of this soon (today hopefully).

@kinkmobile ah, I was hoping for the list of plugins (if you’d rather share it privately, you can email me at dizzy (at) innocraft (dot) com). My current guess is that code from another plugin is interfering with Matomo for WordPress (specifically it’s ability to autoload files).

Since this error only appears during archiving, something else you could try is enabling the “Enable archiving via HTTP request” option at Matomo Analytics > Settings > Advanced.

@markzoi I see, in that case the real error message will be in the PHP error logs. If you are willing to look for them, we’d certainly appreciate it, but since your immediate issue is resolved, it’s understandable if you don’t want to spend more time on this. For now I’ll mark this issue as resolved (you’ll still be able to comment here, though).

@kinkmobile thanks for letting us know you are also affected by this specific issue. We will include a better error message, earlier on so affected users can apply the above fix early without having to reach out to support.