QSO not logged if I enter a locator - database error truncation on COL_DISTANCE

[sipsmi]

I just upgraded to 2.4.11 from an earlier version.

If I log a QSO AND put in a locator it does not log.
Switching on developer mode gives the error below - anyone know what may be amiss?

A Database Error Occurred
Error Number: 1265

Data truncated for column 'COL_DISTANCE' at row 1

INSERT INTO `TABLE_HRD_CONTACTS_V01` (`COL_TIME_ON`, `COL_TIME_OFF`, `COL_CALL`, `COL_BAND`, `COL_BAND_RX`, `COL_FREQ`, `COL_MODE`, `COL_SUBMODE`, `COL_RST_RCVD`, `COL_RST_SENT`, `COL_NAME`, `COL_COMMENT`, `COL_SAT_NAME`, `COL_SAT_MODE`, `COL_COUNTRY`, `COL_CONT`, `COL_QSLSDATE`, `COL_QSLRDATE`, `COL_QSL_SENT`, `COL_QSL_RCVD`, `COL_QSL_SENT_VIA`, `COL_QSL_RCVD_VIA`, `COL_QSL_VIA`, `COL_QSLMSG`, `COL_OPERATOR`, `COL_QTH`, `COL_PROP_MODE`, `COL_IOTA`, `COL_DISTANCE`, `COL_FREQ_RX`, `COL_ANT_AZ`, `COL_ANT_EL`, `COL_A_INDEX`, `COL_AGE`, `COL_TEN_TEN`, `COL_TX_PWR`, `COL_STX`, `COL_SRX`, `COL_STX_STRING`, `COL_SRX_STRING`, `COL_CONTEST_ID`, `COL_NR_BURSTS`, `COL_NR_PINGS`, `COL_MAX_BURSTS`, `COL_K_INDEX`, `COL_SFI`, `COL_RX_PWR`, `COL_LAT`, `COL_LON`, `COL_DXCC`, `COL_CQZ`, `COL_STATE`, `COL_CNTY`, `COL_SOTA_REF`, `COL_WWFF_REF`, `COL_POTA_REF`, `COL_SIG`, `COL_SIG_INFO`, `COL_DARC_DOK`, `COL_NOTES`, `station_id`, `COL_MY_GRIDSQUARE`, `COL_HRDLOG_QSO_UPLOAD_STATUS`, `COL_QRZCOM_QSO_UPLOAD_STATUS`, `COL_MY_CITY`, `COL_MY_IOTA`, `COL_MY_SOTA_REF`, `COL_MY_WWFF_REF`, `COL_MY_POTA_REF`, `COL_STATION_CALLSIGN`, `COL_MY_DXCC`, `COL_MY_COUNTRY`, `COL_MY_CNTY`, `COL_MY_CQ_ZONE`, `COL_MY_ITU_ZONE`, `COL_GRIDSQUARE`, `COL_EQSL_QSL_SENT`, `COL_EQSL_QSL_RCVD`, `COL_LOTW_QSL_SENT`, `COL_LOTW_QSL_RCVD`) VALUES ('2023-10-30 18:59', '2023-10-30 18:59', 'K1WB', '30m', '', 10126000, 'CW', NULL, '599', '599', 'William A', '', '', '', 'United States Of America', 'NA', NULL, NULL, 'N', 'N', '', NULL, '', '', 'G0FOZ', 'Suffield', '', '', '', 0, NULL, NULL, NULL, NULL, NULL, '75', NULL, NULL, '', '', NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, '291', '5', 'CT', NULL, '', '', '', '', '', '', '', '1', 'IO90CS', 'N', 'N', 'CHRISTCHURCH', '', '', '', '', 'G0FOZ', '223', 'ENGLAND', '', '14', '27', 'OP77', 'N', 'N', 'N', 'N')

Filename: models/Logbook_model.php

Line Number: 551

[sipsmi]

Seems to be related to a JS error in the browser when I enter a locator into the QSO.... INvalid LatLng:object

2leaflet.js:5 Uncaught Error: Invalid LatLng object: (undefined, undefined)
    at new M (leaflet.js:5:2636)
    at C (leaflet.js:5:2856)
    at e.initialize (leaflet.js:5:72465)
    at new e (leaflet.js:5:14732)
    at t.marker (leaflet.js:5:139734)
    at Object.success (qso.js:719:21)
    at u (jquery-3.3.1.min.js:2:27457)
    at Object.fireWith [as resolveWith] (jquery-3.3.1.min.js:2:28202)
    at k (jquery-3.3.1.min.js:2:77651)
    at XMLHttpRequest.<anonymous> (jquery-3.3.1.min.js:2:79907)

[sipsmi]

Well, I guess if you dig hard enough you find the problem.
Seems I had the earlier version's JS cached (probably) and a hard reload seems to have worked. Entering a locator into the log QSO field now shows the distance/bearing and logs the QSO.