Station Logbook creation allows invalid Callsign characters
gx1400 opened this issue · comments
Describe the bug
When creating a new account on my personal Cloudlog instance for my radio club account, I accidentally typed "WA0RC`" as the station call instead of "WA0RC" (note the accent mark). After unloading logs I noticed the mistake and changed it in logbook settings.
Advanced Logbook entries, ADIF exports, and LOTW uploads appeared correct, but when importing from LOTW, no QSO matches would be found. It appeared that maybe when changing the station call in the logbook settings, it did not update the underlying database entries, but when other functions were processed, maybe the updated value was used?
To Reproduce
Create new logbook.
Type callsign but add invalid character.
Expected behaviour
Input should error on invalid characters
Additional context
I resolved by exporting the entire logbook to ADIF, then deleting all logbook entries using the Advanced Logbook and Delete action. I imported QSOs with the previously exported logs. Using this clean ADIF import, Logbook of the World imports now match and update