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
timo-bes opened this issue
Sep 25, 2012
· 6 comments
Labels
BugFor errors / faults / flaws / inconsistencies etc.CriticalIndicates the severity of an issue is very critical and the issue has a very high priority.
Since Piwik 1.8.4, we use the column url_prefix in log_action. The column is nullable but the MYSQLI adapter does not support NULL values. This results in 0 being written into the database for outlinks (that the UI shows http:// twice is correct behavior - the problem is that the data is incosistent).
The text was updated successfully, but these errors were encountered:
If you have experienced this bug, you can fix the damage easily.
First, fix your database:
UPDATE piwik_log_action SET url_prefix = NULL WHERE type != 1;
After that, the visitor log is back to normal.
Then, drop the archives since September 2012. So if you read this in October, you need to drop (i.e. delete) the MySQL tables piwik_archive_blob_2012_09, piwik_archive_blob_2012_10, piwik_archive_numeric_2012_09 and piwik_archive_numeric_2012_10.
If you have browser archiving enabled, the archives will be recreated on demand. If you use the cronjob, run it.
After doing that, the other reports (e.g. outlinks) should be back to normal.
Note: This only works for new actions if you either apply the patch above by hand or have a version of Piwik installed that includes the change (> 1.8.4).
Have you executed the SQL statement AND added the code change? You can do that by either applying [7056] by hand or downloading the latest beta: http://builds.piwik.org/piwik-1.9-b10.zip
BugFor errors / faults / flaws / inconsistencies etc.CriticalIndicates the severity of an issue is very critical and the issue has a very high priority.
Since Piwik 1.8.4, we use the column url_prefix in log_action. The column is nullable but the MYSQLI adapter does not support NULL values. This results in 0 being written into the database for outlinks (that the UI shows http:// twice is correct behavior - the problem is that the data is incosistent).
The text was updated successfully, but these errors were encountered: