Obsolete HTML anchor warning

[epement]

Using Bible Analyzer v5.6.1.04 under Microsoft Windows 10.

In two separate sessions of Bible Analyzer, I searched for a non-existent reference, which generated an error message that I dismissed by clicking on the "OK" in the error popup. I searched within Bible Analyzer again, this time for the word "hope." Bible Analyzer emitted the same warning/error message, even though I had not searched for this term during this instance of Bible Analyzer.

Steps to reproduce the error. I created aliases to search for passages in the Bible, and to search for Bible words. Aliases can be created in several ways under Windows: with Take Command, with Cmder, or with DOSKEY macros. I invoked two search commands which pulled up Bible Analyzer, and then closed Bible Analyzer before invoking the search again.

My user prompt is the current working directory in square brackets, a newline, the current time in square brackets, followed by a right angle bracket, ">".

Code: Select all

[c:\users\ericp]
[ 2:32] > gen 3:36

[c:\users\ericp]
[ 2:33] > bible hope

Those aliases "gen" and "bible" expand to these values. The "%$" is a TCC operator that represents all the parameters on the command line.

Code: Select all

[c:\users\ericp]
[ 2:45] > alias gen
bibleanalyzer://bible/gen_%$

[c:\users\ericp]
[ 2:45] > alias bible
bibleanalyzer://search+av/%$

Error message that appeared when I ran the 2nd command, "bible hope", searching for the word "hope".
.

BA_ref_warning2.jpg (43.1 KiB) Viewed 14795 times

.

Are you able to reproduce this error? If you need help or further details, please let me know and I will help.

Kind regards,

[Tim]

I believe the issue here is when the reference is from a link, and the ref is not valid, when Bible Analyzer starts the next time it attempts to display the invalid ref again.

I need to fix it so an invalid reference is not saved, but in the meanwhile simply select a valid ref in the Bible Panel to make it the current ref before closing.

[epement]

Thank you, Tim. Your readiness to fix it is a blessing.

I also tested your solution of searching for a new, valid reference, and that did the trick!