Bug: Logos 3 steals control of libronixdls links

A number of users are reporting that updating Logos 3 breaks Logos 4 libronixdls link function in notes, on the internet and elsewhere.

As it is currently recommended that we install both Logos 3 and Logos 4, IMO you should ensure updating Logos 3 doesn't break this Logos 4 feature. The simple way of doing so would be to check the registry settings on a Logos 4 startup.

Find more posts tagged with

Comments

Dave Hooton

The problem I noted to Bradley in October was that Logos4 broke the Logos 3 registry setting HKCR\libronixdls\DefaultIcon, not the other way around! The Libronix name is not associated with Logos 4 and I expressed surprise that L4 was usurping an L3 registry setting!

HKCR\libronixdls\shell\open\command and HKCR\libronixdls\DefaultIcon = L4 path to Logos4.exe

HKLM\Software\Classes\libronixdls\shell\open\command AND DefaultIcon = L3 path to LDLSexec.exe

(HKCR = HKEY_CLASSES_ROOT)

Mark Barnes

https://community.logos.com/discussion/comment/51113#Comment_51113

Those registry settings (which are in essence the same) should both point to L4, or at least to the application you now use as default. They control what happens when you click on a libronixdls hyperlink in web-pages and in notes. Logos4 still creates hyperlinks prefixed by libronixdls when you coupy location to clipboard as a URL(e.g. libronixdls:jump|ref=bible.79.2.5|res=LLS:1.0.710).

Dave Hooton

https://community.logos.com/discussion/comment/51144#Comment_51144

Logos4 still creates hyperlinks prefixed by libronixdls when you coupy location to clipboard as a URL

Ok! I think I get it. The only libronixdls key that points to L3 is HKLM whilst HKCR, HKCU & HKU point to L4. My L3 Notes still jump to L3. If I paste a libronixdls link in the Command bar it jumps as expected (to L3 from L3, to L4 from L4). I suspect that a web page would always jump to L4 because your link went there. The L4 install usurped L3 but did it do so correctly?

Mark Barnes

https://community.logos.com/discussion/comment/51160#Comment_51160

The webpage links can be over-ridden by the browser, so it's not certain your registry is correct just because the link went there. A better test is the link within L4 notes.

The problem is caused if you update L3 (e.g. to 3.0g) after you have installed L4. If you've never done this then I expect everything works fine for you.

Dr. Charles A. Wootten

https://community.logos.com/discussion/comment/51113#Comment_51113

HKCR\libronixdls\shell\open\command and HKCR\libronixdls\DefaultIcon = L4 path to Logos4.exe

HKLM\Software\Classes\libronixdls\shell\open\command AND DefaultIcon = L3 path to LDLSexec.exe

(HKCR = HKEY_CLASSES_ROOT)

Just letting you know that I followed this discussion and eventually had a moment to change the registry in Windows 7. This now works just great! The link that Mark put in an earlier comment on this thread opened in L4 whereas before the change it opened in L3. Either was fine, but I'm starting to really get used to L4.

There was a similar discussion on the thread that begins, "External Resource Hyperlinks to L3....."

thanX!! guys.

God bles

{charley}

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/51160#Comment_51160

Logos4 still creates hyperlinks prefixed by libronixdls when you coupy location to clipboard as a URL

Ok! I think I get it. The only libronixdls key that points to L3 is HKLM whilst HKCR, HKCU & HKU point to L4.

HKLM points to LDLS3 (because it installs machine-wide).

HKCU normally points to Logos 4 (because it installs per-user). However, running the 3.0g update overwrites this value to point back to LDLS3, which stops links opening in Logos 4.

HKCR is not its own storage location, but simply a unified view of HKLM\SOFTWARE\Classes and HKCU\Software\Classes.

To fix the problem, open Registry Editor, navigate to HKEY_CURRENT_USER\Software\Classes\libronixdls\shell\open\command, and change the (Default) value to:
"C:\Users\USERNAME\AppData\Local\Logos4\Logos4.exe" %1

Dave Hooton

https://community.logos.com/discussion/comment/51378#Comment_51378

To fix the problem, open Registry Editor, navigate to HKEY_CURRENT_USER\Software\Classes\libronixdls\shell\open\command, and change the (Default) value to:
"C:\Users\USERNAME\AppData\Local\Logos4\Logos4.exe" %1

This appears not to be regarded a bug so we need to notify every user to make a change to their registry!

Rich DeRuiter

https://community.logos.com/discussion/comment/52217#Comment_52217

This appears not to be regarded a bug so we need to notify every user to make a change to their registry!

Dave, I suspect that the next install of 4.0a will fix this automatically.

Or it could, if Logos set up the install that way. [suggestion?]

[It's generally a bad idea to tell your average user to change their registry - let alone all of them.]

Dave Hooton

https://community.logos.com/discussion/comment/52227#Comment_52227

[It's generally a bad idea to tell your average user to change their registry - let alone all of them.]

It's a workaround and it's all we have for the moment - http://wiki.logos.com/Bug$3a_Logos_3_steals_control_of_libronixdls_links

Rosie Perera

https://community.logos.com/discussion/comment/51144#Comment_51144

Those registry settings (which are in essence the same) should both point to L4, or at least to the application you now use as default. They control what happens when you click on a libronixdls hyperlink in web-pages and in notes. Logos4 still creates hyperlinks prefixed by libronixdls when you coupy location to clipboard as a URL(e.g. libronixdls:jump|ref=bible.79.2.5|res=LLS:1.0.710).

libronixdls hyperlinks don't work for me at all. It doesn't matter whether I have L4 or L3 running. When I click on a libronixdls link (such as the one above, or one created in L4 by doing "Copy as URL" or "Copy as Wiki" and pasting into a wiki page), the Logos icon on the taskbar flashes once, but the program doesn't open up to the Bible verse specified.

Rosie Perera

https://community.logos.com/discussion/comment/55189#Comment_55189

Those registry settings (which are in essence the same) should both point to L4, or at least to the application you now use as default. They control what happens when you click on a libronixdls hyperlink in web-pages and in notes. Logos4 still creates hyperlinks prefixed by libronixdls when you coupy location to clipboard as a URL(e.g. libronixdls:jump|ref=bible.79.2.5|res=LLS:1.0.710).

libronixdls hyperlinks don't work for me at all. It doesn't matter whether I have L4 or L3 running. When I click on a libronixdls link (such as the one above, or one created in L4 by doing "Copy as URL" or "Copy as Wiki" and pasting into a wiki page), the Logos icon on the taskbar flashes once, but the program doesn't open up to the Bible verse specified.

After weeks of this not working for me, I've got it working finally! Yeehaw! See http://community.logos.com/forums/t/9019.aspx.

Rosie Perera

https://community.logos.com/discussion/comment/71673#Comment_71673

I had fixed this and it was working fine, but I've been back to using Logos 3 for a couple of things recently and it grabbed the libronixdls protocol back again. I don't want to have to keep editing it back to point to Logos 4. What a pain! I can't wait to be able to ditch Logos 3 altogether. Has anyone else experienced L3 stealing your libronixdls protocol back again, changing your registry?

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/74898#Comment_74898

With Logos 4.0d, run

%LOCALAPPDATA%\Logos4\Logos4.exe /register

to re-register all Logos 4 protocols (including libronixdls:) with Logos 4.

(On Windows XP, run
"%USERPROFILE%\Local Settings\Application Data\Logos4\Logos4.exe" /register
)

Rosie Perera

https://community.logos.com/discussion/comment/146992#Comment_146992

With Logos 4.0d, run

%LOCALAPPDATA%\Logos4\Logos4.exe /register

to re-register all Logos 4 protocols (including libronixdls:) with Logos 4.

(On Windows XP, run
"%USERPROFILE%\Local Settings\Application Data\Logos4\Logos4.exe" /register
)

Cool! Thanks. Are there any other documented (or un-documented) command-line switches? I'd like to set up a wiki page to document them. I know about logosref, logosres, and logos4 URIs that can be passed to ExecuteUri, as you mentioned that the other day. But in that post you said they were the only command line arguments Logos supports, and that clearly isn't the case. Anything else up your sleeves? At least anything that might be helpful to MVPs helping people troubleshoot something? [;)]

Dave Hooton

https://community.logos.com/discussion/comment/146992#Comment_146992

With Logos 4.0d, run

%LOCALAPPDATA%\Logos4\Logos4.exe /register

to re-register all Logos 4 protocols (including libronixdls:) with Logos 4.

(On Windows XP, run
"%USERPROFILE%\Local Settings\Application Data\Logos4\Logos4.exe" /register
)

This has been added to the wiki at http://wiki.logos.com/Hyperlinks together with a command for custom installations:-

drive:\<path>\Logos4\Logos4.exe /register

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/147060#Comment_147060

Cool! Thanks. Are there any other documented (or un-documented) command-line switches? I'd like to set up a wiki page to document them. I know about logosref, logosres, and logos4 URIs that can be passed to ExecuteUri, as you mentioned that the other day. But in that post you said they were the only command line arguments Logos supports, and that clearly isn't the case. Anything else up your sleeves? At least anything that might be helpful to MVPs helping people troubleshoot something?

I forgot about this one (because we don't have any documentation on it ourselves...) [:$]

The only other command-line argument I think that there is is "/lang:es" to force a specific UI language to be used (given the ISO 639-1 code). This, of course, can already be changed in General Settings.

Rosie Perera

https://community.logos.com/discussion/comment/147253#Comment_147253

The only other command-line argument I think that there is is "/lang:es" to force a specific UI language to be used (given the ISO 639-1 code). This, of course, can already be changed in General Settings.

Thanks! I've added a wiki page: http://wiki.logos.com/Command_line_arguments

We also need some documentation of the logosref, logosres, and logos4 protocols. I couldn't find any doc for these anywhere on the wiki or the forum. Could you send me what you've got?

tom

https://community.logos.com/discussion/comment/147253#Comment_147253

because we don't have any documentation on it ourselves...

This is scary - very scary.

It is statements like this and Bob's "Code first, optimize later" that has made my confidence with Logos drop like a rock (along with L4 roll-out and,...). As a software developer, I cannot see how you have anything that is not documented. How do you all do maintenance on your code without documentation? I can see if the code is 20 to 30 years old, but L4 is not that old, and good software development practices have been in place for the industry for years.

Rich DeRuiter

https://community.logos.com/discussion/comment/147321#Comment_147321

because we don't have any documentation on it ourselves...

This is scary - very scary.

It is statements like this and Bob's "Code first, optimize later" that has made my confidence with Logos drop like a rock (along with L4 roll-out and,...). As a software developer, I cannot see how you have anything that is not documented. How do you all do maintenance on your code without documentation? I can see if the code is 20 to 30 years old, but L4 is not that old, and good software development practices have been in place for the industry for years.

Just because Bradley isn't in the group of people who have documentation, does not mean there is no documentation for these things. Logos compartmentalizes code development in various departments. The fact that not all departments share everything is not at all unusual, nor unexpected.

Rosie Perera

https://community.logos.com/discussion/comment/147321#Comment_147321

I can see if the code is 20 to 30 years old, but L4 is not that old, and good software development practices have been in place for the industry for years.

Young, small software companies rarely adhere to good software development practices that have been in place in the industry for years. There's a tradition that goes before them, but because they have only just entered that tradition they usually think they can transcend it by being smarter, working harder, and not being enslaved by old practices and "processes" that were developed by big companies and are perceived to be bureaucratic and unnecessary. This is the way entrepreneurship usually works, and it's a necessary stage. But there's a reason those big companies got to be successful and big. I know it's nice to stay small and nimble and idealistic, and often that is enough to carry a company along for a while. But eventually it has to grow up and act like a mature company, or the costs of not doing so will bite it in the end. I love Logos, and I love their responsiveness to their users, the ability for us to dialogue directly with developers, the fact that the CEO is personally involved in design decisions and communicates on the user support forum and takes responsibility for mistakes. I don't want them to get big and bureaucratic. But I do hope they begin to realize the value of some of the more time-tested software development practices that they have yet to adopt. Having a dedicated Testing team, for example.