Thanks for reporting this. I can reproduce this behavior, and it does look like a bug. I'll open a case for it.
[resolved]Prayer List Help
Doug Hanna
Member Posts: 81 ✭✭
I just started using Logos to organize my prayer lists. I have different prayers assigned to different days (e.g. I want to pray for Bob on Monday, Frank on Tuesday, John on Wednesday, etc.).
I have several different lists, and when I open each one up I can see which prayers are assigned for today:
However, on the homepage, it's just a list of all the prayers on that list in alphabetical order. It's not helpful for what I want to do (prayer for certain things on certain days).
Because I have so many different lists, it really is not an ideal situation to open up each one. I have to be missing something - is there a setting to change the display of Today's Prayers on the homepage so that it will only show.... today's prayers?
The only support I was able to find online was a Wiki article about Logos 4.
0
Comments
-
Thanks for reporting this. I can reproduce this behavior, and it does look like a bug. I'll open a case for it.
0 -
Thanks for reporting this. I can reproduce this behavior, and it does look like a bug. I'll open a case for it.
Awesome! Glad to know this is being looked at! Thanks Jacob!
0 -
This has been fixed internally and will go out in an upcoming release
0 -
Jonathan Haas said:
This has been fixed internally and will go out in an upcoming release
Awesome! Thanks Jonathan! This will serve me and other users greatly!
0 -
Not to Hi-Jack Doug's thread, but is there a way to delete a prayer list once it's created? I've created two separate prayer lists by accident, and now need to delete one of them. On the list I want to delete, do I need to mark all items as answered? I would rather delete the whole list.
0 -
Matthew Wyenandt said:
is there a way to delete a prayer list once it's created?
Right-click on the prayer list in the Documents menu and choose the Delete option
0 -
That's too easy!!! Thanks, Graham.
0 -
Jonathan Haas said:
This has been fixed internally and will go out in an upcoming release
This has been fixed in 6.1.
0
