FreeDATA Version
0.17.6-beta
What operating system are you using?
Windows
Operating System Version
Win 11
Architecture
x86
Area of problem
Server - General
Describe the bug
In the settings tab you can fill in a malformed QTH locator.
To Reproduce
Go to Settings / Station
Fill in an locator, for example JOA1fe (mine is JO21fe)
Go to Settings / Web
Activate "Publish station details"
Expected behavior
A check with a popup stating why the locator is wrong.
Screenshots
No response
Log Files
No response
Additional context
My locator is JO21fe, I deliberately gave a wrong one : JOA1fe.
In the console :
2025-08-28 22:11:06 [info ] Running BeaconCommand invalid literal for int() with base 10: 'A1'
You could easily overlook this check and it will be only visible if the beacon is activated.
In the Explorer this probably resulted in throwing the error on line 113 of hamgridsquare.js.
I believe that the Publish station details causes this wrong qth locator to be pushed to the Explorer api as it got not sent over the air.
FreeDATA Version
0.17.6-beta
What operating system are you using?
Windows
Operating System Version
Win 11
Architecture
x86
Area of problem
Server - General
Describe the bug
In the settings tab you can fill in a malformed QTH locator.
To Reproduce
Go to Settings / Station
Fill in an locator, for example JOA1fe (mine is JO21fe)
Go to Settings / Web
Activate "Publish station details"
Expected behavior
A check with a popup stating why the locator is wrong.
Screenshots
No response
Log Files
No response
Additional context
My locator is JO21fe, I deliberately gave a wrong one : JOA1fe.
In the console :
2025-08-28 22:11:06 [info ] Running BeaconCommand invalid literal for int() with base 10: 'A1'
You could easily overlook this check and it will be only visible if the beacon is activated.
In the Explorer this probably resulted in throwing the error on line 113 of hamgridsquare.js.
I believe that the Publish station details causes this wrong qth locator to be pushed to the Explorer api as it got not sent over the air.