I have created a custom guide called "Taylor Bible Study Guide" (Cheezy I know...) When I look in the guide section I see that I have 2 searches completed but it will not allow me to see them as with the standard guides. Any thoughts?
Hi David
I created one as well - and it seems to work fine as below:
For it to show up in the guide section I needed to name it in the top section of the guide as shown.
Are you doing that?
What are you seeing?
Graham
I click the arrow to expand the list under my search. It immediately goes back and closes the list. There are three dots to show that logos is trying to do something but it happens so fast I can't even get a screenshot of it.
This was a problem which was seen during beta testing but was fixed.
Looks like it might have crept back in somehow.
Suggest you modify the title of your thread to include a "BUG:" heading.
This was a problem which was seen during beta testing but was fixed. Looks like it might have crept back in somehow.
In another thread, someone on the beta channel said this bug would be fixed when 5.0a is released.
Donnie
Hi Donnie
This was a problem which was seen during beta testing but was fixed. Looks like it might have crept back in somehow. In another thread, someone on the beta channel said this bug would be fixed when 5.0a is released. Donnie
Are you referring to this one - http://community.logos.com/forums/t/59463.aspx - if so it seems to be a slightly different problem
Tes is having this problem also: http://community.logos.com/forums/p/59877/426023.aspx
Thanks Steve - and yes, this is fixed in 5.0a Beta.
Hopefully that release will be out soon so I can use my guides again
Hi David,
i haven't upgrade to L5, but on another user's machine we could click on Title (on the right side of the guides drop down) and the stuff showed up. You might also use the Find box (when showing by Title).
Thanks Graham!
Tried the find box, no luck.
Did you click on the Name column before using the Find box? (to the best of my memory)
Yes. Apparently there are others who are having the same issue as I am.
I think it should be fixed as a Service Release, but it sounds like 5.0a may be coming soon.
