How do I suppress the new open URL behavior?

No, I don't remember when the behavior changed but when I click on a link in a word document it now opens the web application - which is very annoying when I want it to open in the copy of Verbum or Logos that I already have open on my desktop. What do I need to set to return to a preference for the desktop application?

Find more posts tagged with

Desktop App

Comments

David Taylor, Jr.

[Y]

Levi Durfey

I agree completely--it's so annoying to have to go through the web-app as a middle-man!

Dave Hooton

when I click on a link in a word document it now opens the web application

Obviously, it depends on how the link was created, but ref.ly has become the default for easily creating links in third party docs or web pages.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1089210#Comment_1089210

iOS and Android have added the ability for applications to register the ability to handle https://ref.ly/ links (so that the app opens directly when a link is clicked, not a browser).

Windows and macOS don't currently have any such functionality, but we will take advantage of it (to bypass the browser) if it's ever supported.

NB.Mick

https://community.logos.com/discussion/comment/1089249#Comment_1089249

when I click on a link in a word document it now opens the web application

Obviously, it depends on how the link was created, but ref.ly has become the default for easily creating links in third party docs or web pages.

Yes, but in the - somewhat recent - past, while the web app used to open when clicking a ref.ly URL reference, it gave control to the open Logos desktop installation (and I seem to remember the web app opening the desktop program which was installed, if it wasn't running), which subsequently opened the linked resource.

Nowadays, the web app is the end - which is irritating. In fact I hate the seemingly convenient button we now have in the new store which offers to "Open in Logos" but only opens it in the web app. I then have to close the web app and still need to locate the work in the library or through the command box, what a waste.

Maybe someone should ask this thread to be moved to the web app subforum, because I don't think this is a Logos 8 bug but a bug (or unwanted and undiscussed design change) in the web app causing this.

NB.Mick

https://community.logos.com/discussion/comment/1089272#Comment_1089272

Windows and macOS don't currently have any such functionality, but we will take advantage of it (to bypass the browser) if it's ever supported.

I definitely believe I remember this worked in the past - not totally bypassing the browser, but having the web app open the Logos program to the right resource.

Levi Durfey

https://community.logos.com/discussion/comment/1089274#Comment_1089274

I definitely believe I remember this worked in the past - not totally bypassing the browser, but having the web app open the Logos program to the right resource.

This is how it works for me on macOS. It loads the resource in the web app, then Safari pops up a warning box, "Do you want to allow this page to open in Logos?" After I click "Allow," it opens the resource in the desktop version of Logos.

NB.Mick

https://community.logos.com/discussion/comment/1089278#Comment_1089278

I definitely believe I remember this worked in the past - not totally bypassing the browser, but having the web app open the Logos program to the right resource.

This is how it works for me on macOS. It loads the resource in the web app, then Safari pops up a warning box, "Do you want to allow this page to open in Logos?" After I click "Allow," it opens the resource in the desktop version of Logos.

This is the way it used to work in the early days of URL-Links. Then either FL changed something or Chrome remembered me allowing it, anyway, for a time it just opened he resource in the desktop application without asking. Now it does neither.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1089283#Comment_1089283

It still works that way on Windows, too:

Maybe this is controlled by one of Chrome's many preferences? You may be able to fix it by clicking the lock icon next to "app.logos.com", then "Site Settings", then "Reset permissions".

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1089337#Comment_1089337

Or it looks like there might have been a change in a recent version of Chrome that negatively impacts the Logos 8 experience with ref.ly (and Zoom and RingCentral and other apps): https://support.google.com/chrome/thread/14193532?hl=en

NB.Mick

https://community.logos.com/discussion/comment/1089337#Comment_1089337

Maybe this is controlled by one of Chrome's many preferences? You may be able to fix it by clicking the lock icon next to "app.logos.com", then "Site Settings", then "Reset permissions".

This didn't work for me.

MJ. Smith

https://community.logos.com/discussion/comment/1089343#Comment_1089343

Makes sense - I use Chrome and the change in behavior didn't appear to line up with a Logos release.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1089337#Comment_1089337

If you're getting prompted with this dialog every time, it appears that there is a Chrome Enterprise Policy that will add a checkbox to make Chrome remember your decision: https://cloud.google.com/docs/chrome-enterprise/policies/?policy=ExternalProtocolDialogShowAlwaysOpenCheckbox

If you're not getting prompted with this dialog at all, then perhaps a) Chrome has remembered that you don't want to open an external application for this protocol, or b) there's an error in app.logos.com that's preventing it from appearing. For (a) I haven't been able to find any additional information on how to control this yet; for (b) opening Dev Tools and looking for errors in the console might identify if there's a problem with the site.

NB.Mick

https://community.logos.com/discussion/comment/1089340#Comment_1089340

Or it looks like there might have been a change in a recent version of Chrome that negatively impacts the Logos 8 experience with ref.ly

Hm. I tried Edge (I dislike it but it comes with Win 10, so it was lying around) and clicking the "Open in Logos" link - for today's homepage deal resource, to be precise - which invokes the web app did not open the book in the desktop program either. Seems either Logos is not registered to accept the request or the web app is not sending it to the OS.

MJ. Smith

https://community.logos.com/discussion/comment/1089356#Comment_1089356

Playing with various combinations on Chrome, it appears that if the call originates within Chrome I get the popup asking if I want the application or the web. However, if the call originates outside of Chrome it simply opens the web app. There may be other factors playing a role but ...

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1089357#Comment_1089357

Logos is not registered to accept the request

Yes, it's possible the registration was damaged. Assuming Logos is installed in the standard location, you can try repairing it by running:

%LOCALAPPDATA%\Logos\Logos.exe /register

NB.Mick

https://community.logos.com/discussion/comment/1089379#Comment_1089379

Logos is not registered to accept the request

Yes, it's possible the registration was damaged. Assuming Logos is installed in the standard location, you can try repairing it by running:

%LOCALAPPDATA%\Logos\Logos.exe /register

Thanks! Successfully registered Logos (nonstandard location, but I found it) and now ref.ly links work as intended: Web app opens the resource, subsequently opens Logos desktop application - yes, even if the program was closed - and opens the resource there: perfect. I tested with this link: https://ref.ly/logosres/9781461660545?art=r1 from the topics.logos.com Reading Lists site. And it even works for products I don't own, like https://ref.ly/logosres/CRSSSHATTRDCHRIST

Unfortunately, the implementation of the "Open in Logos" button does not use ref.ly links but links directly to the app, such as https://app.logos.com/books/LLS%3aGODETSTNT which will not trigger the "Open in Logos" behavior. The ref.ly links will end up in the app in an URL that looks like this (e.g. https://app.logos.com/books/LLS%3ACRSSSHATTRDCHRIST ) but it seems that only when the link is in ref.ly format to begin with, the web app will invoke Logos desktop.

Good for the links we build in Word documents, webpages and wherever, bad for "Open in Logos" which won't ever open Logos. I'll carry that one to the logos.com subforum, thanks again for your help, Bradley!

Edit: thread over there is https://community.logos.com/forums/t/188595.aspx