Files
OpsLog/internal
rouggy f8fdfab031 fix(hamlog): a status AND a date, like every other service
Bulk edit offered two HAMLOG fields, both dates, and the first question they
drew was the right one: which of these is the status? Collapsing the flag into
the date was neat in the storage and a riddle in the dialog, where the eight
fields above it are four status/date pairs.

So four keys now — APP_OPSLOG_HAMLOG_SENT / _SENT_DATE and _QSL / _QSL_DATE —
and four fields, in the shape an operator already reads for eQSL, QRZ, Club Log
and HRDLog. The stamp written after a successful upload follows: Y in the
status, the day in the date.

Nothing else changes: the QSL Manager's backlog still asks whether the sent key
is present, and the award engine still treats any non-N value in the QSL key as
a confirmation.
2026-08-23 13:14:05 +02:00
..
2026-08-02 20:03:16 +02:00
2026-07-03 19:08:50 +02:00
2026-07-04 11:39:33 +02:00
2026-08-20 17:53:55 +02:00
2026-08-21 18:21:33 +02:00
2026-08-21 18:21:33 +02:00
2026-08-02 23:51:46 +02:00
up
2026-06-15 23:45:14 +02:00
2026-06-07 01:11:37 +02:00
2026-08-21 01:43:14 +02:00
2026-08-21 18:21:33 +02:00
2026-08-21 18:21:33 +02:00
2026-06-11 21:54:35 +02:00
up
2026-06-15 23:45:14 +02:00
2026-07-09 17:32:13 +02:00
2026-08-21 18:21:33 +02:00
2026-08-02 06:40:10 +02:00