Chapter missing notes / Won't allow for creation of notes

Have an interesting dilemma. I'm studying Isaiah and have notes in each chapter, but noticed today that one of the chapters is not only missing all my notes but it does not allow me to start all over on that chapter and create more notes. All the other chapters (that I've checked thus far) are not missing any notes and will still allow me to create more. I've reloaded the page on my computer as well as tried fixing it by simply restarting the computer. Don't suppose anyone else is dealing with this?

Which chapter?

LOL, I'm not sure it matters, but it's chapter 25.

LauraClayton wrote: Thu Jul 06, 2023 6:30 am LOL, I'm not sure it matters, but it's chapter 25.

Knowing which chapter will allow others to try to duplicate the problem... Especially since you have reported that only 1 chapter seems to be affected.

You mentioned you're on your computer – are you using Gospel Library Online in a web browser, Gospel Library for Windows, Gospel Library for iOS on a Mac, or Gospel Library for Android on a Chromebook?

I just tested in iOS Gospel Library and Gospel Library Online and was able to create highlights and notes in Isaiah 25. Maybe there was a temporary glitch with that chapter that was fixed with a content update – are you still seeing the issue?

Thanks! Shows how much I don't know, doesn't it! LOL

I'm using GL for Windows. And chapter 25 still has the issue. Other chapters seem to be working just fine.

Going through my web browser (Firefox 114.0.2 over Windows 10) to the main Church website and then Libraries > Scriptures > Old Testament I have had difficulty getting references in Isaiah to display properly. I can usually fix the error by reloading the page, but not always. This has been going on for several weeks now.

It may be worth the effort for someone to make a quick check to see that the content is coded properly and then linked properly to the website library.

Thanks for your feedback!

Does anyone from this forum have access to the ear of someone who from the Church who deals with checking the codes, etc.?

<<<<<Going through my web browser (Firefox 114.0.2 over Windows 10) to the main Church website and then Libraries > Scriptures > Old Testament I have had difficulty getting references in Isaiah to display properly. I can usually fix the error by reloading the page, but not always. This has been going on for several weeks now.

It may be worth the effort for someone to make a quick check to see that the content is coded properly and then linked properly to the website library.>>>>>

For the Windows Gospel Library issue where you can get to Isaiah 25, but can't create notes or highlights there, your best bet may be to send feedback through the app. In the iOS and Android apps, the feedback form is under Help > Send Feedback (the option may be slightly different in the Windows app).

lajackson wrote: Fri Jul 07, 2023 8:20 am Going through my web browser (Firefox 114.0.2 over Windows 10) to the main Church website and then Libraries > Scriptures > Old Testament I have had difficulty getting references in Isaiah to display properly. I can usually fix the error by reloading the page, but not always. This has been going on for several weeks now.

It may be worth the effort for someone to make a quick check to see that the content is coded properly and then linked properly to the website library.

Is the issue you're seeing on Gospel Library Online where, when you try to open a single chapter, it redirects to the Old Testament table of contents? I've been having that happen too, over the past week. I was able to get in contact with someone on the Gospel Library Online team and they found a potential fix, which should hopefully go out soon.

sbradshaw wrote: Thu Jul 13, 2023 5:00 pm Is the issue you're seeing on Gospel Library Online where, when you try to open a single chapter, it redirects to the Old Testament table of contents? I've been having that happen too, over the past week. I was able to get in contact with someone on the Gospel Library Online team and they found a potential fix, which should hopefully go out soon.

Yes. It happened more often than not, but it was intermittent and I got there by a different path, so I had not yet sent in a bug report. It has not happened at all this week.