[resolved] BUG (6.1 RC1): Final section of books cannot be printed/exported
1. Open a book.
2. Select Print/Export
3. Select the very last section. It won't appear. If you deselect everything else, either the document will be blank, or the second-to-last-section will appear.
4. Select a bunch of previous selections, or all previous sections, and the last section. Oftentimes all pages will be blank. Either way, the last section never appears.
Some examples of books I tested this with:
- Logos Help
- Verbum Help
- Treasury of Scripture Knowledge
Comments
-
Fr Devin Roza said:
- Treasury of Scripture Knowledge
In Treasury of Scripture Knowledge I don't get anything other than blank pages for any books after Philemon
0 -
Fr Devin Roza said:
1. Open a book.
2. Select Print/Export
3. Select the very last section. It won't appear. If you deselect everything else, either the document will be blank, or the second-to-last-section will appear.
4. Select a bunch of previous selections, or all previous sections, and the last section. Oftentimes all pages will be blank. Either way, the last section never appears.
Some examples of books I tested this with:
- Logos Help
- Verbum Help
- Treasury of Scripture Knowledge
We have an active case for this issue. I'll add a link to this thread, and we'll update it once it's fixed. Thanks for the report!
0 -
Hi Dylan
Dylan Rondeau said:We have an active case for this issue. I'll add a link to this thread, and we'll update it once it's fixed. Thanks for the report!
Thanks for that[Y]
And do you think the issue reported at https://community.logos.com/forums/p/101147/699058.aspx#699058 might be related as well?
Graham
0 -
I have implemented a fix for this issue internally; we will update this thread when the fix ships publicly. Thank you!
0 -
Chris Culy (Faithlife) said:
I have implemented a fix for this issue internally; we will update this thread when the fix ships publicly. Thank you!
Thanks Chris
Appreciate the update, Graham
0 -
Chris Culy (Faithlife) said:
I have implemented a fix for this issue internally; we will update this thread when the fix ships publicly. Thank you!
This should be fixed in 6.3 Beta 1.
0 -
0
