[resolved]Change Home Page Settings but changes don't show up

I've opened up the "settings" and selected several items such as "Logos Blog" and "Verbum Blog" and "Logos Pre-Pubs. However the changes to not take affect - usually. I using Verbum and I believe when I open Verbum it's set work online. I've tried setting it to "work Offline" and then tried setting it to open "on-line". This doesn't seem to have an impact. However, once and a while, when I open Verbum all the selection will show up. I've tried rebooting my Windows 7 computer and then restarting Verbum. This does not seem to be the answer. The only thing that always shows up from the "Content" section of the Settings is "From your library" - which I do have selected.

I'd appreciate any thoughts on what I could do to have all my selections from the Settings options show up.

Thanks for your help.

Greg Rose

Find more posts tagged with

Comments

MJ. Smith

Try F5 to refresh the page after you have changed the settings and close the setting windows.

If that doesn't work, show us what you are trying to change. Remember that not all blogs are daily and that they may appear anywhere in the page.

Jacob Carpenter (Faithlife)

Greg:

We've identified a bug that could cause the issue you're describing. 6.3 beta 1 should contain a fix for this issue.

Greg Rose

Thank you very much. F5 works. Sometimes I have to press it several times but it does do the trick.

Greg Rose

Thank-you for the response. I was wondering about the 6.3 beta 1 version though. When I check the version number of Verbum using the "about Verbum" help it currently indicates "Verbum 6.1 SR-36.1.0.0038" I'm using the Bible software almost every day so I would think I'm up-to-date on the latest version. Was there a version 6.2 that was never pushed out? Or could version 6.3 be the Logos 6 version but not the Verbum software version? Thanks again for your help.

MJ. Smith

6.2 is in RC at the moment ... so new changes are going into 6.3 ... 6.2 will be released shortly

Angela Murashov

6.2 is in RC at the moment ... so new changes are going into 6.3 ... 6.2 will be released shortly

6.3 is now available on the stable channel and should include a fix for this issue.