Bug in PBB Resource Linking? File Attached

Joseph Turner · 2025-02-15T01:46:00+00:00

There was an error rendering this rich post.

I am trying to update the Denver Annotated Bibliographies, and one of the things I'm doing this time around is updating all resource linkis to the new URL format (https://ref.ly/logosres/resourceid) as opposed to the depricated L4 links (logosres:resourceid).

Only some links work, and the links that work change based on each build. Once, all the links worked, but when I changed one of the resource links, it messed up again.

There are no relevant errors that would indicate an issue.

All links work when clicked from the Word document.

Any ideas what's going on?

OT2025_0_0.docx

Find more posts tagged with

Files

Bug

Desktop App

Comments

Dave Hooton

https://community.logos.com/discussion/246499/bug-in-pbb-resource-linking-file-attached

I compiled the first 5 pages and found that the ref.ly links worked (those I do not own came up with a Preview).

(Windows 11, Logos 39.1).

Submit a part of the docx where links do not work for you (or are unstable) and state the metadata you used in the Personal Books tool (I used Type monograph and Language English).

Joseph Turner

Hey Dave, I'm sorry. I forgot that I posted this here before I posted it in the Beta forum. It turned out that for some reason, Word (I have the newest version) converted some of the hyperlinks into the <w:instrText> format as opposed to the <w:hyperlink> format. I simply had to click on one of the working links and apply that style to all of the hyperlinks in the document. That fixed it.

Strangely, when two others saved my document in Word on their computers, the links corrected themselves and worked, as they apparently did on your computer. Mine would not do so without doing what I stated above.

To be clear, this was a strange Microsoft Word issue and had nothing to do with Logos, except that Logos couldn't recognize the incorrect link type.

Dave Hooton

https://community.logos.com/discussion/comment/1358604#Comment_1358604

That's OK Joseph. I'm glad it is resolved.