Reading plan not showing up on homepage but present in Documents
Yesterday I deleted a completed reading plan on my desktop (L5.0a on Windows 7) and created a new one.
When synchronised to my iPad, the deleted one disappeared but the new one did not show up on my homepage although it is visible as a document on my iPad
I wonder if the sync event contained both the deletion and the creation of the new plan which has caused the homepage to be only partially updated.
Any thoughts on this would be appreciated and any suggestions on how to get the Reading Plan to show on the homepage?
(I guess that simply deleting it and recreating it would fix this but thought I would flag this first to see if anyone has any insights!)
The new Reading Plan does appear on my homepage in the Bible app on Android and in FSB on iPad.
And just I was writing this post it appeared on the homepage of my Bible app on iPad!
So looks like some strange synchronisation issue.
I thought I would leave the post for if anyone else sees the same thing in the future.
Thanks, Graham
Comments
-
-
For clarification: the new plan didn't appear at first, but it has appeared now. Is that right?
Correct
What day was the new reading supposed to begin?
Yesterday, Friday
What day was it when you didn't find the plan?
I didn't find it on the homepage on Friday evening but did find it on my iPad as a Document and read it from the links in the document and marked it as read.
This still did not cause it to appear on the iPad homepage
It did appear today - Saturday morning - just as I was posting my original note in this thread
Was the reading current, or still future?
Not quite sure what you mean.
The document was updated correctly and it now shows correctly on the homepage - that the next reading is for Monday as per the plan.
0 -
-
By "current" and "future" I was hypothesizing that the reason the plan didn't show up is because it was still "future" and that there weren't any "current" readings. In other words, the reading plan hadn't begun yet.
Understand now - thanks.
But no, in this case, there were current readings.
Strange[:)]
0