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
The problem is solved when
a) in core/DataTable.php, function unserializeRows.php, add right before ‘return $rows’: if(!is_array($rows)) { $rows = array(); }
b) in core/DataAccess/ArchiveSelector.php, function querySingleBlob, change line 646 to: if(is_array($blobs)) { ksort($blobs); }
There seems to be empty data rows which at least has to be an empty array.
If this is true, how does it happen, what is the best was to clean the data?
What should happen?
archivephp cron job should not break for specific tracked webpages
The text was updated successfully, but these errors were encountered:
rolf-siepmann
added
Potential Bug
Something that might be a bug, but needs validation and confirmation it can be reproduced.
To Triage
An issue awaiting triage by a Matomo core team member
labels
Dec 4, 2024
What happened?
Please check: https://forum.matomo.org/t/serialization-error-while-archiving/61411, especially:
The problem is solved when
a) in core/DataTable.php, function unserializeRows.php, add right before ‘return $rows’: if(!is_array($rows)) { $rows = array(); }
b) in core/DataAccess/ArchiveSelector.php, function querySingleBlob, change line 646 to: if(is_array($blobs)) { ksort($blobs); }
There seems to be empty data rows which at least has to be an empty array.
If this is true, how does it happen, what is the best was to clean the data?
What should happen?
archivephp cron job should not break for specific tracked webpages
How can this be reproduced?
e.g.: /usr/bin/php /var/www/piwik/console climulti:request --matomo-domain=“https://xxx/” --superuser “module=API&method=CoreAdminHome.archiveReports&idSite=58&period=year&date=2024-01-01&format=json&trigger=archivephp”
Matomo version
5.1.2
PHP version
8.3.14
Server operating system
Ubuntu 22.04.5 LTS
What browsers are you seeing the problem on?
No response
Computer operating system
No response
Relevant log output
Validations
The text was updated successfully, but these errors were encountered: