Mark Bubeck, Craig Bubeck, Fire From Heaven: God's Provision for Personal Spiritual Victory - Looks interesting.
https://vyrso.com/product/18592/fire-from-heaven-gods-provision-for-personal-spiritual-victory
Thanks. Looks like a good read.
[y]
Looks good [Y]
On my IPad, when a chapter is selected it attempts to open it in my web browser outside the app. Is anyone else able to replicate this problem? Thanks
I just checked three chapters in my copy of the book on my iPad and they all opened fine. Which chapter is doing this for you?
In the table of contents, all the chapters do this. I've never had this problem before. I tried restarting the app, but it continues doing it. Thanks Bruce.
I checked the chapters from my table of contents too so something is definitely not working correctly for you but I guess you already knew that. I actually did a fresh reinstall tonight on one of my iPads because it wasn't working correctly. Perhaps that may be needed for you too but I would start with killing the app and starting it again.
I just tried it on Logos 6 on my Mac, and can confirm—clicking on the chapters in the table of contents tries to open a website instead of going to the chapter.
Here's an example of URL it tries to open: http://1-ignitinggodspeopletojointhebattle.html/#Anchor
Can I ask which chapter(s) are doing this for you?
All of them—I think the issue is the same or similar to the issue here: https://community.logos.com/forums/t/113487.aspx
It may be related as you say but it is interesting that I am able to navigate all of the chapters using the table of contents. What version of the app are you using? Right now I'm using 4.6.3 (4.6.36071). I have not updated to the newest version yet. Perhaps the newest version is causing the issue.
As I mentioned above, I am seeing this in Logos 6 on my Mac.
It seems like a problem with the eBook conversion process, but I can't figure why it's working for you. You must be special.
Just tried on my iPhone using (4.6.4)—problem exists there also.
Bruce, I'm using the latest version (4.6.4) on my IPad.
So far, I am only seeing this problem in this particular resource.
I'm not sure what is going on. I just updated my software and to 4.6.4 on my iPad and checked my iPhone that is using 4.6.4 and they both still work. Sometimes digital devices can be very strange.
for clarification: are you using the TOC page, or the TOC feature in the software? Using the TOC page, I am taken to my web browser. As I explained in another thread, some ebooks utilize .html in thier navigation. Obviously that carried over in the conversion.
for clarification: are you using the TOC page, or the TOC feature in the software?
Yes I am using the TOC in the software and it takes me to the correct chapter when I choose any of the chapters.
Using the TOC page, I am taken to my web browser.
This is not happening to me.
Using the TOC page, I am taken to my web browser. This is not happening to me.
Its not happening to me either
for clarification: are you using the TOC page, or the TOC feature in the software? Yes I am using the TOC in the software and it takes me to the correct chapter when I choose any of the chapters.
this should be the case for everyone, as the sidebar TOC utilizes headings to create the TOC.
when you click on the blue hyperlink, you are taken to the right place? Did you just purchase this resource, or did you already own it?
Here are screen shots:
Clicking on chapter 1, safari opens having tried to open an html web page based on the chapter name. This happens on both desktop and mobile.
Utilizing the built in TOC produces the expected behavior:
Bama, now I feel really dumb. [:$] Upon further examinations I didn't understand your terminology but now I know what you mean. When I use the TOC I only use it from "within the software" as you call it so that what was messing me up. I'm getting the same results as you are now.
No problem. [:)] You did have me quite perplexed. [:D]
Using the TOC page, I am taken to my web browser. This is not happening to me. Its not happening to me either
And you? Can you confirm the behavior or do you still not see it?
Hi, everyone.
I can confirm the behavior on app.logos.com, which makes me think that's all the platforms. (So a book bug, rather than an app bug.)
Steps: Open the book (resource details below) and scroll down until you see the "Contents" article with a list of blue hyperlinks. (Do not use the app's builtin "Table of Contents" feature/pane. This is generated from the h1, h2, etc tags in the book and has no relationship -- except coincidentally -- to the article called "Contents" which you get to by scrolling down.)
Issue: The Foreword, Preface, Acknowledgements, and Introduction work as normal (click/tap them and jump to the proper part of the book). But all of the Chapter links (for example, "1. Igniting God's People to Join the Battle") open in a browser.
Solution: The issue seems to be an encoding error in the ePub files from the publisher that made it through our automatic conversion process. We'll need to update and rebuild the resource to fix it.
Workaround: In the meantime, if you use the app's built-in table of contents feature or pane rather than following the links from the Contents article in the book, you should be able to navigate within the resource just fine.
Title: Fire From Heaven: God's Provision for Personal Spiritual VictoryResource Id: LLS:61CC905270271A494F81DE23E6F4B528
Thanks!
Hi Eli
(So a book bug, rather than an app bug.)
But may not be limited to just one book - see https://community.logos.com/forums/t/113533.aspx for a similar discussion about another resource
Graham
Thanks Eli. [:)][Y]
Thanks, Graham. It's probably a bug or mishandled markup (or just as likely, a publisher ePub convention we haven't seen before). In any case, we'll end up fixing it in the conversion code.
Using the TOC page, I am taken to my web browser. This is not happening to me. Its not happening to me either And you? Can you confirm the behavior or do you still not see it?
I can confirm as well. Like Bruce I too misunderstood.
Thanks for clarifying John. [:)]
It's probably a bug or mishandled markup (or just as likely, a publisher ePub convention we haven't seen before). In any case, we'll end up fixing it in the conversion code.
Much appreciated Eli.
