In response to another forum post I was testing the search argument person:Jesus INTERSECTS sense:"to fulfill (prophecy)" INTERSECTS sense:messiah which failed on the second term. While trying to correct it, the app closed. 2045.VerbumError.zip
Thanks for the logs, I see a failed GET request in the file that caused the host to force close.
Going back to the search query, can you elaborate on this part.
While trying to correct it, the app closed
For starters, the query gave you a unknown data type value correct? From there, what did you do to correct it if possible before the crash?
Things I've tried:
1. Adding different text where prophecy was (not sure what to change it to though)
2. Shortened the query to see if different results came through.
Should the query be ever valid and actually run if so, what's that query?
I cut the third term and its operator to add back in and was trying to get an autocomplete suggestion for the fulfill term ... ditching the prophecy portion assuming an autocomplete of any kind would resolve the problem.
I haven't a clue. The argument string came from a forum post who got it off a Facebook page ... he gave no indication of what he thought it would do. His question was conversion of the format from L9 to L10. see Search problem - Logos Forums
I apologies as I misspoke about the log file, and for any confusion it may have caused you. It sounds like the specific log file we need is called logos.log or verbum.log in this case. If it's possible, it would be helpful for us if you could upload the whole zip file but nonetheless, we'll need the verbum.log file.
If you don't have the log file on hand, it would be useful if you could try to recreate the scenario and generate that log file. We've checked some internally crash reports, but unfortunately, they didn't provide any insight on the issue. We are here to help, but without that log file, we may be limited in our ability to assist.
Thanks again!
The log file quit being built in the folder a few versions back ... I have a standard installation ... no playing with folders, permissions, or redirects ... I had run the script to turn logs on permanently.
I had run the script to turn logs on permanently.
It is weird. I thought logs were automatically enabled for Betas - mine are. Holding the CTRL key whilst you start should enable logging.
