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
Meanwhile, we have identified the cause: Sometime after the version 1.10.1 four new fields for the table log_visit have been introduced, one is called "config_os_version". In our intranet many user sessions are running under Citrix. The corresponding calculated value for this field is "Server 2003". With this value, the write operation goes wrong. The complete record is not written.
The call Piwik_Tracker getDatabase :: () -> query ($ sql, $ bind) in Visit.php is not coming back, the action is not counted!.
So 3,500 visitors per day with all actions are lost in our statistics.
The text was updated successfully, but these errors were encountered:
In 16f8dd6: Fixes #4203 DevicesDetection 1.14 version schema update to account for longer strings ( fields config_os_version and config_device_type are not large enough )
Refs #4204 Plugin schema example with DevicesDetection
In ded987a: Fixes #4203 DevicesDetection 1.14 version schema update to account for longer strings ( fields config_os_version and config_device_type are not large enough )
Refs #4204 Plugin schema example with DevicesDetection
…account for longer strings ( fields config_os_version and config_device_type are not large enough )
Refs matomo-org#4204 Plugin schema example with DevicesDetection
sabl0r
pushed a commit
to sabl0r/piwik
that referenced
this issue
Sep 23, 2014
…account for longer strings ( fields config_os_version and config_device_type are not large enough )
Refs matomo-org#4204 Plugin schema example with DevicesDetection
These two fields can be longer than 10 characters, which may fail to record properly when some special settings are set in mysql such as strict mode.
Reported in forums
The text was updated successfully, but these errors were encountered: