Closed int2001 closed 1 year ago
I'd love to have it so that when importing ADIFs that Cloudlog could figure out the MY fields and check if a locations missing and build it. but yes think a warning might be needed for v1 to v2 i'd hope not many are running v1 now
100% ACK. but normally there's no way to import ADIFs (or QSOs via API) without a station_id, fixed the last bugs which can cause that (hopefully) in the last release.
so this bug appears only when old qsos without station_id exists.
Thanks for filing this after my comment in the draussenfunker Discord @int2001!
Potentially related: I imported some different adifs today and it mentioned that not all fields are valid, but it didn’t say what’s wrong. I’d have to experiment again with the adif files.
I’m not 100% sure if the warning appeared prior to the imports and was caused by a recent instance update or was caused by the imports.
created a patch for that at https://github.com/magicbug/Cloudlog/pull/2353
Admin can reassign QSOs:
Describe the bug QSOs without a station_id (set to NULL) can only be updated to station_id=1
To Reproduce Steps to reproduce the behaviour:
On Multiuser-instances, that's not good, because every User who calls "Station Locations" ist able to do that. Even if he isn't owner of Station_id=1.
Expected behaviour Don't know. Lets discuss. Ideas so far:
i think this is an edge-case and only occurs when you're updating from v1 to a more actual Version. Normally QSOs without a station_id shouldn't exist...