Title says it all. On the majority of my logs, when I type in a callsign, it will bring up a preview window of the name, flag, and person’s name. It doesn’t always pull in the name displayed, or state/country the preview shows. Is it something I’m doing wrong?
2 Likes
@W8CBG The third party database we use to source callsign details has been having some issues. We switch to a backup service when there is an outage, and we are preparing our own database to eliminate these issues altogether. When did this start happening?
Andy N0APX
WRL Product Manager
1 Like
It’s been several weeks now at least. The preview shows the name and state, but it won’t populate the actual fields of the contact automatically.
2 Likes
Okay, gotcha. We’re having more issues with our third party lookup service, but we are implementing backup services to keep everything running smoothly. Let me know if you have any more issues!
1 Like
For some reason - it has been working on my PC, but not on my Win11 mini laptop that I wanted to use for live logging.
2 Likes
@W8CBG I would ensure that you have a stable internet connection and maybe try clearing the browser cache. If it still doesn’t work let us know and we’ll take a look to see if something else is going on. Thank you!
Andy N0APX
WRL Product Manager
1 Like
I am maintaining two logbooks. When coping, I must select the log book I want the QSO entered into. When the selected logbook opens, the QSO information is blank, it is not entered and I must enter the info manually.
Is this typical for multiple logbooks? Thank you.
2 Likes
@K3UD Are you moving QSOs from one logbook to another using QSO manager?
1 Like
No. QSOs from the spotting page were not populating the fields in the logbook I selected. An email from Catalina Ostolaza (World Radio League) on November 16 notified me that this bug was fixed. That issue has been resolved.
73
Timothy Sayers (K3UD)
2 Likes