Recently we encountered problem with accurate lat/long storing when being passed by request parameter.
It looks like it's connected strictly with type of location_latitude and location_longitude columns.
Originally it's float and then error occurs. Altering it to decimal seems to solve problem.
How to reproduce:
Then launch simpliest tracking request like:
and see in database what values are stored:
On the other hand tracker debug show proper values.
After changing schema of log_visit table and launching next request, coordinates are stored properly (lat: 98.230000, long: -21.450000)
Thanks for the report!
This change requires a schema upgrade to ALTER the column types, which is currently blocked: No schema change allowed on log_visit nor log_link_visit_actions nor log_action tables #6953
@tsteur I went the easy route and simply cast the field to decimal. It's working good enough in our case.