ref.ly links in version 40

Dave Hooton · 2025-02-14T00:02:54+00:00

There was an error rendering this rich post.

Dave Hooton

From Share > Copy Link in beta 3:
https://ref.ly/Re3.15-16;nicnt87rev

Whilst understood internally e.g. Command Box, it does not work externally e.g. MS Word

From Share > Copy Link in Logos 39.1:
https://ref.ly/logosres/nicnt87rev?ref=Bible.Re3.15-16

With the workaround, this now goes thru the web app.

What has happened?

Find more posts tagged with

Bug

Comments

NB.Mick

Hm. Running Beta 3 - I see the usual syntax when using share / copy link, even with ctx:

https://ref.ly/logosres/niv2011?ref=BibleNIV.Ge2.1&off=0&ctx=2+~Thus+the+heavens+and+the+earth+%E2%80%A2were+c

this is from right-click menu reference / copy reference: https://ref.ly/Ge2.1

however, now the whole verse is selected and the right-click menu was sitting at "reference" (no longer visible of course), now the share /copy link produces https://ref.ly/Ge2.1;niv2011

Dave Hooton

The behaviour has changed from v39 and there is no indication in the Release Notes.

From Share > Copy Link in beta 3:
https://ref.ly/Re3.15-16;nicnt87rev

If I make page number the active reference, Copy link is:

https://ref.ly/logosres/nicnt87rev?ref=Page.p+109&off=528
this goes thru the web app. But page no. becomes the active reference.

https://ref.ly/logosres/nicnt87rev?ref=Bible.Re3.15-16 from v.39.1 retains the bible reference at both ends.

This is unacceptable to me.

ESV bible Copy link & Copy Special URL is https://ref.ly/Joe3.16
NET bible Copy link https://ref.ly/Joe3.16;gs-netbible & Copy Special URL is https://ref.ly/Joe3.18.

This is just confusing as the first goes to Biblia.

Dave Hooton

https://community.logos.com/discussion/246475/ref-ly-links-in-version-40

The situation is unchanged in RC1 and the https://ref.ly/Re3.15-16;nicnt87rev link goes to Biblia (below) whilst the Logos 39.1 link works thru the web app.

Adam Borries (Logos)

I don't think the issue is the shorter URL format in v40.
https://ref.ly/logosres/nicnt87rev?ref=Bible.Re3.15-16 (in v39)
https://ref.ly/Re3.15-16;nicnt87rev (in v40)
These two links are equivalent URLs. When clicking one of them from an external application (other than a web browser), they should both open the desktop app to the resource with the Bible reference milestone index selected.

Dave, if I understand correctly, the issue is that all refly links (reference or page-number based) in MS Office are opening the browser, rather than opening the desktop app directly. Do those links work as expected in Wordpad? If so, you may need to run the script from this post to fix MS Office.

(There's a secondary issue here, as well: in a web browser, https://ref.ly/Re3.15-16;nicnt87rev opens Biblia.com and doesn't resolve correctly. We'll take a look at that too, but it shouldn't affect the desktop app.)

Dave Hooton

@Adam Borries (Logos) Dave, if I understand correctly, the issue is that all refly links (reference or page-number based) in MS Office are opening the browser, rather than opening the desktop app directly. Do those links work as expected in Wordpad? If so, you may need to run the script from this post to fix MS Office.

Thanks, Adam.
I had applied the Office script fix when it was announced, with good results. But I found it is no longer in the registry! Having re-applied it, the various test links I documented here now work in both Logos 39.1 and Verbum 40.0 RC1 without using the web app.
The apps are installed side-by-side and Logos is preferred as the target provided it is loaded first.

I use Word 365, not Wordpad.

Bradley Grainger (Logos)

But I found it is no longer in the registry!

Is it possible that Office installed a minor update since you ran that script? Perhaps it clears those registry keys when it does?

Dave Hooton

https://community.logos.com/discussion/comment/1359003#Comment_1359003

I don't know, Bradley. But I will know what to do if it happens in the future.