Since latest update (0.3.2), data is not written to database about matomo-for-wordpress

[Findus23]

Looking at the "Visits in Realtime" section on my Matomo dashboard, I do see visits and actions reported in the past 24 hours and even in realtime

So data is actually written in the database properly and just the reports aren't generated properly.

Can you check the system report for errors?

[newmediamadman]

Hi Findus23, thanks for your response. There are indeed some oddities in the System Report (included below; domain name omitted). The message pertains to a cronjob, but I have not made any changes to this. The error seems to coincide with the update to the latest version of Matomo.

Archiving last ran successfully on Sunday, December 1, 2019 20:35:35 which is 1 days 20:02:56 ago.

Please check that you have setup a crontab calling the core:archive console command, and that you have configured a MAILTO to receive errors by email if archiving fails. You can also try to run the console command to archive your reports manually: /home/wp_qwm5g9/website.com/wp-content/plugins/matomo/app --matomo-domain=www.website.com core:archive. Learn more.

[tsteur]

fyi I adjusted the system report to no longer show this message that you need to set up a cronjob as this is actually not correct for WordPress. You don't need to do anything there.

@newmediamadman do you remember which version you were using before upgrading?

Any chance you could copy/paste the full system report output here?

In case you are familiar with error/debug logs, is there any chance you could check either your WP_DEBUG log and/or PHP error log?

[tsteur]

You might also want to test that if you go to Matomo => System Report => Troubleshooting and then click on Archive reports whether the reports appear afterwards?

[tsteur]

No need for WP_DEBUG then for now. I have a very good idea what causes it and will investigate in a few hours. Thanks for that!

[tsteur]

Thanks for your help again @newmediamadman I was able to reproduce and fix the issue after a while and will release a new version soon.

[newmediamadman]

Great -- glad to hear it. Cheers!

…

On Wed, Dec 4, 2019 at 3:52 AM Thomas Steur ***@***.***> wrote: Thanks for your help again @newmediamadman <https://github.com/newmediamadman> I was able to reproduce and fix the issue after a while and will release a new version soon. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#118>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4KEGBZWW4W6BPJOSJ5FODQW4SORANCNFSM4JUUP2EA> .

[newmediamadman]

I just spotted the update, installed it, and can confirm that the report archiving now works and the errors are resolved. Thanks!

…

On Wed, Dec 4, 2019 at 8:38 AM Lars Nyman ***@***.***> wrote: Great -- glad to hear it. Cheers! On Wed, Dec 4, 2019 at 3:52 AM Thomas Steur ***@***.***> wrote: > Thanks for your help again @newmediamadman > <https://github.com/newmediamadman> I was able to reproduce and fix the > issue after a while and will release a new version soon. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#118>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AA4KEGBZWW4W6BPJOSJ5FODQW4SORANCNFSM4JUUP2EA> > . >