Replies: 4 comments 9 replies
-
Do you by chance know what MySQL version your using? |
Beta Was this translation helpful? Give feedback.
-
Just to keep working I added a line - if ( ! isset($dxcc) || empty($dxcc)) { return '' ; } - so the code does not fail and this allows to log calls I have not seen before - will dig deeper when I get a minute.
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
I ran into the same issue after I updated cloudlofg from 2.5.? to 2.6.14. So I tried updating the country informations but this hasn't solved the problem. Also clearing the browser cache has no effect. I changed the lookup callbook from 'qrz' to 'hamqth' an the issue disappeared for know. I looking forward this issue will be solved soon. thank you for your work. Maybe some additional helpful informations:
Cloudlog Version 2.6.14 |
Beta Was this translation helpful? Give feedback.
-
Yes I have cleared the cache.
Normally when logging a QSO the system shows previous QSOs with that user and looks up name in QRZ. This works for some calls I have worked with but since 2.6.2 I have issues logging/lookups for many callsigns. The error log seems to suggest an SQL error (see below). Any pointers to what may be going on here?
This seems to be mainly an issue with callsigns I have not worked before. If I try logging a call I have previously worked all the fields fill in and the QRZ/HAMQTH icons appear next to the call.
Cheers
Si G0FOZ
Beta Was this translation helpful? Give feedback.
All reactions