You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the visits log is disabled globally or in website setting, loading reports for a period that has not yet been archived (without browser trigger), might currently show the error "Visits log is deactivated in website settings..."
The problem seems to be that the raw data check might try to perform a request to Live.getLastVisitsDetails in
That method is not available with deactivated visit log.
We should check if we can use or create another API method that provides the needed information, or maybe avoid the call completely if it doesn't make sense in that case.
The text was updated successfully, but these errors were encountered:
Nice find 👍 I actually ran into this issue recently and by the time I wanted to create a bug report I couldn't reproduce it anymore. Likely because data had been archived by then vs in the beginning it hadn't. And DEV-2830 is probably the same issue.
A very quick fix for this and similar issues would be to introduce a new API method like getMostRecentVisitsDateTime. That would allow any part of Matomo to check if there are visits for the current period even if getLastVisitsDetails is disabled in config.
This could actually also be some performance improvement for those parts currently checking this using getLastVisitsDetails...
When the visits log is disabled globally or in website setting, loading reports for a period that has not yet been archived (without browser trigger), might currently show the error "Visits log is deactivated in website settings..."
The problem seems to be that the raw data check might try to perform a request to
Live.getLastVisitsDetails
inmatomo/plugins/CoreHome/vue/src/ReportingPage/ReportingPage.vue
Lines 275 to 279 in 6ab9923
That method is not available with deactivated visit log.
We should check if we can use or create another API method that provides the needed information, or maybe avoid the call completely if it doesn't make sense in that case.
The text was updated successfully, but these errors were encountered: