40.0 Beta 3: New Bug in PBB Resource Linking?

Joseph Turner
Joseph Turner Member Posts: 2,870 ✭✭✭

I haven't used PBB in a little while, so I'm not sure if this is a new bug or not. Here's my post from the other forum that I posted before I realized I was on Beta:

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.

Disclaimer:  I hate using messaging, texting, and email for real communication.  If anything that I type to you seems like anything other than humble and respectful, then I have not done a good job typing my thoughts.

Comments

  • NB.Mick
    NB.Mick MVP Posts: 16,124

    Observations:

    I see probably the same as you. Some links work (like Hamilton's NICOT Gen vol. 2), some don't (like the same, vol 1, needless to say I own both in my library). I can see which ones will work, since those that don't are a lighter shade of blue.

    But: this is consistent, the links seemingly work/don't work totally the same in the book I compiled on Logos 40 Beta 3 and the one I compiled on Verbum 36.1 "old stable"

    Have joy in the Lord! Smile

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 12,037

    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).

    If you have a working link in the source document, there's no need to update it; the PBB compiler will continue to recognize logos4: links.

    Only some links work, and the links that work change based on each build.

    Thanks for posting the source document. I took a look, and it appears that Word is encoding hyperlinks in two different ways: <w:hyperlink> vs <w:instrText>HYPERLINK "https://ref.ly/logosres/nicot01ge1"</w:instrText>. The PB compiler only recognises the former format. I'm not sure why Word would choose to vary how hyperlinks are saved in the DOCX file, but this explains why it seems to arbitrarily change from one build to another.

    I've reported this to the team, but I'm not sure how quickly a fix for this issue could be developed.

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 12,037

    FWIW, I opened your document in my copy of Word (Microsoft® Word for Microsoft 365 MSO (Version 2501 Build 16.0.18429.20132) 64-bit), saved it, and it rewrote all the hyperlinks in the working format. What version of Word are you using?

  • NB.Mick
    NB.Mick MVP Posts: 16,124

    Wow, the same workaround seems to work for me! Microsoft® Word 2016 MSO (Version 2501 Build 16.0.18429.20132) 64 Bit

    Have joy in the Lord! Smile

  • Joseph Turner
    Joseph Turner Member Posts: 2,870 ✭✭✭

    Thank you both. Bradley's information helped me figure it out. I have no idea why the hyperlink types got changed, but I was able to go to one of the entries that had the <w:hyperlink> and change the Hyperlink Style to match that one. That fixed it for all.

    I have no idea why it changed in the first place. It's also strange that you both just saving it fixed the issue for you. I even saved it down to 97-2003, tried it with no help, and then saved it back to modern, with still no help. I have the same version of Word as both of you. Weird.

    Thanks for helping me get it sorted. I was definitely a Word issue and not a Logos issue.

    Disclaimer:  I hate using messaging, texting, and email for real communication.  If anything that I type to you seems like anything other than humble and respectful, then I have not done a good job typing my thoughts.