-
-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On upgrade QRZ icons & lookup not working for new stations #3074
Comments
My first suggestion would be to turn on logging in /application/config/config.php and check for any errors in /application/logs However you could also try //index.php/logbook/json/2M0SQL/0/2m/FM/ That should do a lookup against the callbook you have setup in config.php and if you have still got "development" mode turned on in index.php you should see any errors that might be affecting things.. That would be my first steps |
That sort of error makes me think of an issue with the country files I'd quickly do a Admin -> Update Country files and let it run until it says done and see if the errors still there |
Thx... error from photo solved, but now i get blank page..... and don't get data from qrz.com xml :( |
have you got a paid account on QRZ does changing it to HamQTH with a login make any difference etc |
Hi, sorry for the delay in replying life, work etc - downloaded the latest version and tried again. I am seeing ERROR - 2024-04-28 15:54:56 --> Query error: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 1 - Invalid query: select name, cqz, lat, 'long' from dxcc_entities where adif = So did the county updates a suggested after someone and ran your supplied URL and got the same. A Database Error Occurred Error Number: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 1 select name, cqz, lat, 'long' from dxcc_entities where adif = Filename: models/Logbook_model.php Line Number: 4306 Any thoughts? Thanks Stuart G7JYF |
Cloudlog 2.6.11 (dev), QRZ.com lookup when creating a new QSO still does not work...
|
@magicbug how to debug this error? There is no more information in th cloudlog logfile and in the mariadb error log. |
Without knowing part of the codes triggering that error it will be impossible you'd need to check errors above and below that to see what part of the codes causing it |
For my error -What do you need to know, I enter in the callsign and it writes that to the log. Gone back to paper logs meanwhile and would like to using it? Thanks Stuart |
@magicbug I could describe steps how to reproduce it. But I do not know how to find the SQL request generated by Cloudlog during new callsign lookup at qrz.com. Could you help me to find this SQL query? Steps to reproduce:
|
Hi, I did an export and fresh install and reimported my data and it seems to work now .. as this has other comments on it other than mine and I am fixed. Not tried an update yet but not related. |
Upgraded my local version from 2.4.5 to v2.6.8 using the zip replacement.
I have found that my QRZ lookup does not work nor do the icons appear for new stations that I have not worked before which the previous version did.
When I roll back it works fine.
Previous version entering in a new callsign and then pressing tab the QRZ/HAM icon appears and and the details on the right, after upgrade I see nothing on pressing tab.
I have tried refreshing my browser cache (mac firefox) and also tried in in Safari and my ipad
Server Software Apache/2.4.6 (CentOS) PHP/7.4.33
PHP Version 7.4.33
MySQL Version 5.5.5-10.5.24-MariaDB
Browser. Firefox 124.0.2 (64-bit)
MAC: 14.4.1 (23E224)
The user name and password for QRZ is correct in my config.php
It does seem to work if I use a callsign that I have previously worked, so put in previously works callsign all works as expected, put in new callsign does not do the lookup or show the icons in either live or post QSO screens.
Any suggestions, many thanks
Stuart
G7JYF
The text was updated successfully, but these errors were encountered: