BUG: Personal Book Builder - Input Boxes Not Working On Mac Version
This has been an issue since an update to Logos 8 in December 2019. The following is a link to that Post: https://community.logos.com/forums/p/187089/1081192.aspx#1081192
The following is a link to the second attempt to get this fixed: https://community.logos.com/forums/p/191791/1106676.aspx#1106676
The following is the error log from the test I did today with the following input:
Test input box:
{{ input id=NOTE1-1 | type=text | lines=4 | prompt=“notes” }}
[Info] Starting build for PBB:263a9050c1364f5dbd1f72dc6c343c05
[Info] Converting
[Info] Converting /Users/explorer7/Documents/Bible/Logos Personal Books/Test input box.docx
[Info] Compiling
[Warning] empty style for name D1_Normal
[Warning] empty style for name D1_DefaultParagraphFont
[Warning] empty style for name D1_TableNormal
[Warning] empty style for name D1_NoList
[Error] Error while building book: Error compiling resource.
[Error] Exception: LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookBuilderException: Error compiling resource.
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter.CompileResource (Libronix.DigitalLibrary.LicenseManager licenseManager, System.String manifest, LDLS4.Panels.PersonalBookBuilderPanel.ResourceDocumentData metadata, LDLS4.Panels.PersonalBookBuilderPanel.IPersonalBookBuildLog buildLog, LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter+TempFiles tempFiles, Libronix.Utility.Threading.IWorkState workState) [0x000de] in /Volumes/Code/Jenkins/workspace/Logos-Desktop-Mac-Beta-Ship/LogosDesktop/src/LDLS4/Panels/PersonalBookBuilderPanel/PersonalBookConverter.cs:511
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter+<CreatePersonalBookWork>d__2.MoveNext () [0x0045b] in /Volumes/Code/Jenkins/workspace/Logos-Desktop-Mac-Beta-Ship/LogosDesktop/src/LDLS4/Panels/PersonalBookBuilderPanel/PersonalBookConverter.cs:147
at Libronix.Utility.Threading.AsyncWorkerTask`1[T].EnumMoveNext () [0x0001a] in B:\ghe_actions-2.272.0\Logos-Utility\_work\Utility\Utility\src\Libronix.Utility\Threading\AsyncWorkerTask.cs:120
at Libronix.Utility.Threading.AsyncWorkerTask`1[T].EnumMoveNextWithCatch () [0x00002] in B:\ghe_actions-2.272.0\Logos-Utility\_work\Utility\Utility\src\Libronix.Utility\Threading\AsyncWorkerTask.cs:141
--- End of stack trace from previous location where exception was thrown ---
at Libronix.Utility.Threading.AsyncWorkItem.Verify () [0x0000b] in B:\ghe_actions-2.272.0\Logos-Utility\_work\Utility\Utility\src\Libronix.Utility\Threading\AsyncWorkItem.cs:80
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookViewModel+<CreatePersonalBookWork>d__137.MoveNext () [0x0011e] in /Volumes/Code/Jenkins/workspace/Logos-Desktop-Mac-Beta-Ship/LogosDesktop/src/LDLS4/Panels/PersonalBookBuilderPanel/PersonalBookViewModel.cs:727
Comments
-
bump for visibility 10
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Bump...
Please advise if this is on any Logos action lists.
Thank you,
Rick
0 -
Still an issue with version 9.5
Please address this issue.
Thank you.
0 -
Hi Rick,
As I mentioned in your first thread we do have a case for this. I've brought it to the team's attention again.
0 -
Thank you, it is good to know that there is still an active case on this issue.
0 -
Following up...
I've been having the same issue since version 9.5. I recently updated to version 9.6 and the issue has not been resolved. Please notify when there is a solution.
0 -
This is still an issue with version 9.7
Please address this issue.
Thank you.
0 -
This is still an issue with version 9.9
Please address this issue.
Thank you.0 -
Still an issue with version 9.15... Spent over an hour in frustration trying to figure this out myself until I found this thread. Pretty upsetting considering I only use Apple products and this feature is KEY for my use of personal books.0
-
Still an issue with version 9.15... Spent over an hour in frustration trying to figure this out myself until I found this thread. Pretty upsetting considering I only use Apple products and this feature is KEY for my use of personal books.0
-
-
Hi JT,
The following is what I have been using to check if this has been fixed:
Test input box:
{{ input id=NOTE1-1 | type=text | lines=4 | prompt=“notes” }}
I also attached the same in a Word document.
Thank you for looking at this.
0 -
-
I just tested this and used your docx file and the PB compiled correctly ....
The PB log file reads:
Info] Starting build for PBB:b4e6c0e68d024717b0dae868198b56c4
[Info] Converting
[Info] Converting
\Users\Wolfgang\Desktop\8321.Test input box.docx
[Info] Compiling
[Warning] empty style for name D1_Normal
[Warning] empty style for name D1_DefaultParagraphFont
[Warning] empty style for name D1_TableNormal
[Warning] empty style for name D1_NoList
[Info] Discovering
[Info] CompleteI am running Logos 9.15.0.0005 on Win 10 computer.
Wolfgang Schneider
(BibelCenter)
0 -
Thank you JT.
0 -
Wolfgang,
The Input Boxes work on Windows computers, but not on Mac OS.
0 -
Wolfgang,
The Input Boxes work on Windows computers, but not on Mac OS.
Ah ok ... I missed the detail that you were referring to Mac. Thanks for pointing it out to me.
Wolfgang Schneider
(BibelCenter)
0 -
SO this will never be fixed for Mac users? [:(]
0 -
When will this work
0 -
Same here bro. Very disappointed in Logos. Considering quitting logos
0 -
"The Input Boxes work on Windows computers, but not on Mac OS."
Same here bro. Very disappointed in Logos. Considering quitting logos
Consider asking this question in the Desktop Beta Forum where v23 is being tested (it is supposed to automatically upgrade most users from versions earlier than the current v22, incl. Logos 9).
Dave
===Windows 11 & Android 13
0 -
Any updates on this[:^)]
0 -
-
Any updates on this
Your post is in an L9 forum. You need to post in a current forum.
That's a problem I see in other software companies too. They bring a new version, without fixing all the old bugs. Make a new forum for the new version and the old bugs will never get fixed.
It should be in the responsibility of the company to fix it, even it is an old bug, not in the responsibility of the bug reporter to run after the if the fix to do even the bug is on the old version.
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
😧😧😧
0 -
How would I do that
0 -
-
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0
