I can confirm the bug.
My testfile is here: 2350.Test links.docx
I pasted your references into MS Word as plaintext, then hit space after each one to make them active links in Word (I had previously tested that all of them work from my chrome browser). Then I built the PB "plain vanilla" as type:monograph in lang:English
The four ref.ly/logosres-links are not recognized as links in the PB, whereas the one ref.ly/logos4-link (to the sense of "to watch carefully") does work.
The PBB-log shows three errors
[Error] The 'textpos' attribute must be a LogosResourcePosition parameters dictionary.
Running 8.13 Beta 1 on Windows 10.
PB Build Errors: [Error] The 'textpos' attribute must be a LogosResourcePosition parameters
Tim Hensler
Member Posts: 1,546 ✭✭✭
When I compiled my Bible PB, I got 728 errors between "[Info] Starting build" and "[Info] Discovering", all the same message:
[Error] The 'textpos' attribute must be a LogosResourcePosition parameters dictionary.
I didn't find any reference to "textpos" in the Logos Wiki.
I did not get this error message the previous times I built this PB, the last of which was a couple days ago on Logos 8.12 RC 1.
I made less than a dozen small changes to the PB between the last two builds, so it looks like a change was made in the build code that now does not recognize a preexisting syntax (that I already had in my PB that worked before).
Now hyperlinks that used to work in the PB Bible don't work - no preview pop-up when I hover over the hyperlinks and nothing happens when I click on them.
Here are some examples of hyperlinks that worked before but don't now:
- https://ref.ly/logosres/ubshbk69?ref=Bible.Ga5.26&off=919&ctx=d+has+the+sense+of+“~glorying+in+vain+thi
- https://ref.ly/logosres/nac30?ref=Bible.Ga5.22-23&off=0&ctx=envying+each+other. ~A+Catalog+of+Grace+(
- https://ref.ly/logosres/nlt?ref=BibleNLT.Ga5.18&off=44&ctx=cted+by+the+Spirit,+~you+are+not+under+ob
- https://ref.ly/logos4/Senses?KeyId=ws.watch.v.05
- https://ref.ly/logosres/nttxttranscomm?ref=Bible.Ga5.19&off=193&ctx=R+μοιχεια,+πορνεια “~adultery,+fornicatio
If you need the source DOCX file, please let me know where I should email it to.
0
Comments
-
I can confirm the bug.
My testfile is here: 2350.Test links.docx
I pasted your references into MS Word as plaintext, then hit space after each one to make them active links in Word (I had previously tested that all of them work from my chrome browser). Then I built the PB "plain vanilla" as type:monograph in lang:English
The four ref.ly/logosres-links are not recognized as links in the PB, whereas the one ref.ly/logos4-link (to the sense of "to watch carefully") does work.
The PBB-log shows three errors
[Error] The 'textpos' attribute must be a LogosResourcePosition parameters dictionary.
Running 8.13 Beta 1 on Windows 10.
Have joy in the Lord!
0 -
It's the ctx positioning paramer in your ref.ly links. If you take that out, they will work.
Updated file to try out: 8463.Test links.docx
Have joy in the Lord!
0 -
Thank you, NB.Mick, for your testing and recommendations. The changes you recommend aren't possible because of the number of links in this large document that would need to be changed and the time it would take to fix them all.
Hopefully it's a quick fix by Faithlife.
0 -
-
Thank you, Philana. I hope this is a quick fix - it has disabled an important study/teaching function in the PB.
Thank you.
0 -
-
Thanks!
Have joy in the Lord!
0 -
Not quite all there yet - All the links I tested work except for three. I noticed that the links that work are a dark blue font in the Logos PB resource, but the three I found that don't work are a bright blue font.
Attached is an DOCX excerpt from my PB Bible from Rev. 1:1-8. All the links work in this excerpt except the first three links in verse 8; no pop-up preview and nothing happens when you click on them in the Logos PB. The PB builds with no errors or warnings.
If I take the hyperlink address from the DOCX and past it in the GO box in Logos and click the GO button, the proper resource opens to the proper place. All three of these links happen to come from the same resource:
LLS:NTTXTTRANSCOMM
2015-12-03T19:36:51Z
NTTXTTRANSCOMM.logos40 -
Tim Hensler said:
except the first three links in verse 8
In the Word doc, this is actually one link that spans three paragraphs/bullet points. I don't know if the PBB compiler has ever supported this; I suspect it hasn't.
When I removed that (one) hyperlink, then added it back three times (to just the three words in each paragraph), it compiled and worked fine.
0 -
Worked for me too. Thank you Bradley.
And thank you Philana and team Faithlife.
0
