-
-
Notifications
You must be signed in to change notification settings - Fork 192
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
[Logbookadvanced] First version of a logbook with filtering and batch processing of QSL handling. #1847
Conversation
…processing of QSL handling.
Is it intended that pressing "reset" does only reset the input form and does not update the table, i.e. return to the list of all QSOs? |
That's how it's made, but can be changed. |
Ah ok. No worries. Thought it might be a bug. But WAD is OK also :) |
@phl0 refresh and try the reset now :) |
@AndreasK79 this looks really nice, I'm a little short on time but I'll do my best to try this changes |
@hugosilvaparagramanet hope you like it. Thanks for the code and the idea. |
…er executing batch job
@magicbug I think this is pretty close to ready, if not ready for merge. The question is, if this should have it's own menu item. |
@phl0 good idea. I was thinking something like that myself. |
QRX I will push that to a branch. |
The stuff is here: https://github.com/phl0/Cloudlog/commits/2logbooks. If @magicbug also agrees I can PR that to @AndreasK79's branch. |
Agree think we need to keep both for now at least |
So https://github.com/AndreasK79/Cloudlog/pull/17 ;-) |
Have two separate items for logbook and advanced
So... mergetime? |
think so! at least to dev branch for moar testing! :) |
Interesting, i'm guessing older mysql issue on my live setup i'm getting An error ocurred while making the request then loading it and its calling logbookadvanced/search |
Hmm, check dev tools and see if you can pinpoint the error there. |
ERROR - 2022-12-21 14:10:43 --> Severity: error --> Exception: syntax error, unexpected 'string' (T_STRING), expecting function (T_FUNCTION) or const (T_CONST) /home/twom0sql/domains/logbooks.2e0sql.co.uk/public_html/2m0sql/src/QSLManager/QSO.php 12 |
ERROR - 2022-12-21 14:03:25 --> Severity: error --> Exception: syntax error, unexpected 'string' (T_STRING), expecting function (T_FUNCTION) or const (T_CONST) /home/twom0sql/domains/logbooks.2e0sql.co.uk/public_html/2m0sql/src/QSLManager/QSO.php 12
ERROR - 2022-12-21 14:04:10 --> Severity: error --> Exception: Call to a member function result() on bool /home/twom0sql/domains/logbooks.2e0sql.co.uk/public_html/2m0sql/application/models/Logbookadvanced_model.php 135 |
Looks like i was right MySQL server version for the right syntax to use near '' at line 7 - Invalid query: |
Not really sure that is the problem. The queries doesn't use anything special or newer functions. Try to set limit 250 on line 130 in logbookmodel_advanced.php. |
Ignore.. changed to PHP8 and it fixed it. |
This server which only hosts me needs an upgrade |
What version were you running? I'm on 7.4.8 here. |
it was 7.3! |
Right. Should we make sure it works on that version and older? If so, I need to set up a test machine. |
Maybe but I think perhaps not, just support the last "stable" release its fine on 7.4 |
Hi just found this via search and wanted to let you know that the advanced logbook failed on PHP 7.2.24 on Rocky Linux.
I haven't tried with 7.3 as you all seem to use 7.4 and I can confirm it works now. Wasn't sure because the README only shows PHP 7. (7.4.30) |
I am currently running PHP 7.4.33, all I get is "An error ocurred while making the request"... any tip? |
@DL3EL I'm not sure what the lowest 7.4 is. I'm running 7.4.8 on my dev-setup, and it works fine here, so if you can upgrade the version a little bit and try again, that should fix it. |
@AndreasK79 hmm.. I would think, that 7.4.33 is newer than 7.4.8 |
Oops. It should. Can you look in dev tools and see if you see any errors? |
First I called Logbook Overview (1st and 2nd msg) 1st: DevTools failed to load source map: Could not load content for http://192.168.241.99/assets/css/bootstrap-dialog.css.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE 2nd: DevTools failed to load source map: Could not load content for http://192.168.241.99/assets/js/bundle.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE 3rd: jquery-3.3.1.min.js:2 POST http://192.168.241.99/index.php/logbookadvanced/search 500 (Internal Server Error) 4th: jquery-3.3.1.min.js:2 POST http://192.168.241.99/index.php/logbookadvanced/search 500 (Internal Server Error) |
Can you click on the logbookadvanced/search link and see if the error 500 has any more info? |
I need what is under the response link. |
Maybe set the environment to "development" in index.php temporarily to gain more info in the error. |
Finally, with the help of @phl0 we could solve the issue. The root cause was, the upgrade to php 7.4 was only done on the OS level. Apache itsself was still running with php 7.3. Here is, what we did, the server is a Raspberry PI with Buster: For better debug we enabled developer mode (index.php) and increase error level (application/config/config.php) Make sure libapache2-mod-php7.4 is installed for Apache 2 module (root cause) If not, install it: "sudo apt install php7.4-json php7.4-curl php7.4-mbstring php7.4-mysql php7.4-zip php7.4-xml libapache2-mod-php7.4" now the advance Logbook works like charme |
That is great news! Glad it's now working. Good we have a Linux expert with @phl0 here. |
Thanks to @hugosilvaparagramanet for his QSL Manger PR. I took his code, modified and expanded the functionality. It was very interesting to see how things were solved, and I learned several new tricks.
I've renamed it to Logbook Advanced. For now, I've replaced the logbook link with this one.
Some changes from the original PR.
This is basically a logbook with filtering and batch processing of QSL handling.
Feedback is very welcome.
A preview:
I've added database save for updated info from callbook, if this info does not exist in the database.
Might need to dig some more about what info is returned from QRZ or HamQTH,