Skip to content

QSL/eQSL status not always shown in QSO detail view #1356

@sebket

Description

@sebket

This is for reporting bugs with the code, if this issue is regarding setting up on your local server please use the discussions area

Describe the bug
When opening the QSO detail view by clicking on the corresponding callsign, the line "This QSO was confirmed on..." either by eQSL or paper QSL is not always shown, even though the QSO has been confirmed by one or both QSL types which is correctly shown in the list by the green up/down arrows.
I suspect this is for QSOs that I have imported from another logbook software via ADIF file, where only the status of QSL/eQSL was present, but not the date when QSL has been sent/received.

Version Information
We need some information about your versions. You can get all Information in the Admin > Debug Menu

OS: Ubuntu Server 24.04.1 LTS
PHP: 8.3.6
MariaDB: 10.11.8
Wavelog: 1.9

Steps to Reproduce

Click on any QSO entry where QSL/eQSL is marked as sent and received, but (presumably) no date information is present.

Expected Behavior
I think it would be good if the fact that the QSO has been confirmed by QSL/eQSL is displayed regrdless of the presence of date info. Perhaps the line could be changed to simply "This QSO was confirmed." and in case a date is available it could be appended in brackets or in a second line like "Date: 3/3/24" or something like that.

Desktop Information:

OS: Windows 11 Pro
Browser: Firefox
Version: 132.0.2

Best 73 and thank you for wavelog, it's awesome!
Sebastian DL2KSE

Metadata

Metadata

Assignees

No one assigned

    Labels

    wait 4 closeIssue is wating for closing by issuer

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy