OH6KZP

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 62 total)
  • Author
    Posts
  • in reply to: SMS Spotting #16776
    OH6KZP
    Participant

    Hi Art,

    Thanks for your investigative work!

    From a software development perspective, the easiest approach by far would be for the ParksnPeaks developers to include WWFF (also outside AU) in their SMS spotting service. So I encourage you to keep pushing there πŸ™‚

    Developing another service from scratch instead is a lot of work (by unpaid volunteers). I also suspect that motivation to do that would not be very high, since it would essentially be about duplicating something that already exists.

    73
    Kim OH6KZP

    in reply to: [ERROR] Cannot create QSO entry – 2 issues #16626
    OH6KZP
    Participant

    Hi Peter,

    I’ve posted this to the WWFF IT team through https://wwff.co/reporting-bugs-request-new-features/

    73
    Kim OH6KZP

    in reply to: SMS Spotting #16625
    OH6KZP
    Participant

    Hi Art,

    This sounds like an issue that could best be answered/debugged by the developers of ParksnPeaks, where the SMS interface is.

    The WWFF Spotline spotting service has a documented API that is used by other software for integration. Without knowing the details, my impression is that Parksnpeaks.org intends to use it (see https://spots.wwff.co/info under “Apps that integrate with Spotline”), but perhaps there is something with the SMS that still needs work.

    73
    Kim OH6KZP

    in reply to: Agenda Times NOT UTC #16624
    OH6KZP
    Participant

    Hi Len,

    The programmer understands UTC time very well, yes.

    After further study, the issue here is the agenda’s “time plugin” uses the web browser’s native time format. That format is in turn the time format chosen for use by your device. In this case your device appears to use the 12-hour format instead of the 24-hour format.

    The easiest way to fix this is for you to change your device settings to a 24-hour format. For example my own device uses that, and the UTC time shows in 24-hour format without problems.

    73
    Kim OH6KZP

    in reply to: Agenda Times NOT UTC #16609
    OH6KZP
    Participant

    Hi Len,

    Word from the programmer side is that this should now be fixed. They may have missed the first ticket mentioned above.

    Can you check if it works for you as expected?

    73
    Kim

    in reply to: Two references with the same boundary? #16458
    OH6KZP
    Participant

    Hi John,

    Duplicate areas should not exist, so I’ve e-mailed the EAFF manager Estela EA4DE/CX3ACS and asked her to take a look at this case.

    73
    Kim OH6KZP

    in reply to: General Rule Question – Remote Station #16426
    OH6KZP
    Participant

    Hi Yannick,

    Hunters doing remote is just fine. This would probably be good to spell out explicitly in the next edition of the rules.

    73
    Kim OH6KZP

    in reply to: Logsearch database need some update #16405
    OH6KZP
    Participant

    Hej Peter,

    I will create a bug ticket for this at https://wwff.co/reporting-bugs-request-new-features/

    To help the IT developers, can you provide a few specific examples of what you mean and what pages you are looking at?

    73
    Kim OH6KZP

    in reply to: VEFF no longer exists #16400
    OH6KZP
    Participant

    Hi Emma,

    VEFF exists as before, but apparently there is some glitch with the website address forwarding. Please QRX while it’s getting fixed.

    Logs and other materials can be submitted to logs@veff.ca as far as I’m aware.

    73
    Kim OH6KZP

    in reply to: Agenda Times NOT UTC #16387
    OH6KZP
    Participant

    Hi Len,

    The times are showing in UTC for me, so this may be a browser/device-specific issue. I will file a ticket (https://wwff.co/reporting-bugs-request-new-features/) so the developer can follow up with you on it.

    73
    Kim OH6KZP

    in reply to: Directory pdf link not working #16386
    OH6KZP
    Participant

    Hi Edward,

    Please see also https://wwff.co/forums/topic/pdf-directory-2025-02-24-is-not-working/

    This has been filed as a bug previously: a new PHP version broke the plugin used to generate the PDF file.

    In the bug listing, it’s not high in priority right now to be fixed. Do you have a specific need for the PDF in particular?

    73
    Kim OH6KZP

    OH6KZP
    Participant

    Hi Augusto,

    Usually QSOs with a SIG_INFO that doesn’t correspond to a valid WWFF reference causes an error during upload, and the log cannot be uploaded before the error is fixed. This is most commonly encountered when there is a typo in the reference.

    73
    Kim OH6KZP

    in reply to: english version #16301
    OH6KZP
    Participant

    Bonjour Gaston!

    Logsearch is in English, so I’m not sure I understand your question. Can you rephrase?

    In case you have the Google Translator activated on the left-hand bar to some other language than English, please select “English” in the drop down menu.

    73
    Kim OH6KZP

    in reply to: Activation list #16300
    OH6KZP
    Participant

    Hi,

    I’ve filed this at https://wwff.co/reporting-bugs-request-new-features/ to obtain follow up.

    73
    Kim OH6KZP

    in reply to: Hit Max Characters On Callsign Field #16299
    OH6KZP
    Participant

    Hi Stuart,

    Now reported to the WWFF IT team through https://wwff.co/reporting-bugs-request-new-features/

    73
    Kim OH6KZP

Viewing 15 posts - 1 through 15 (of 62 total)
Translate Β»
×