Missing Warning: Custom Reading Plans

I have a complex custom two-year reading plan. It was too complex to create in one sitting, so every few months, and add another bunch of readings to it, always trying to keep ahead of the current date.

Last week, I thought it would be useful to share with my church, so changed the list so it was shared with them. However, having done so, I can no longer edit the reading plan.

I'm not sure why that limitation exists, but more importantly, I should not have lost editing rights without being warned that would happen. My carefully curated reading list is now permanently stuck, unable to be extended — which after 18 months of nurturing is frustrating, to say the least.

Find more posts tagged with

Comments

Andrew Batishko

You can create a copy of the reading plan either using documents.logos.com, or by creating a new custom plan and importing the old plan.

We prevent editing of plans that have been shared, because modification of the plan would potentially destroy the reading status for other people.

Mark Barnes

https://community.logos.com/discussion/comment/886205#Comment_886205

You can create a copy of the reading plan either using documents.logos.com, or by creating a new custom plan and importing the old plan.

We prevent editing of plans that have been shared, because modification of the plan would potentially destroy the reading status for other people.

THANK YOU!

However, I've just discovered a bug :-).

I noticed that there was an option for "Disconnect from Group" (or words to that effect). I wasn't sure what that would do, so I made a private copy of the document, then disconnected the original document. When I synced Logos, it crashed.

There's nothing in the log, and no call stack in event viewer. This is all I get:

Application: Logos.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFB6AE30074
Stack:

When I restarted Logos, everything was well.

PS — Given that it's possible to disconnect at documents.logos.com, surely it would be logical to allow that in the app as well? I can't be the only one who didn't realise it was possible.

Mark Barnes

https://community.logos.com/discussion/comment/886207#Comment_886207

There's a second bug, unfortunately.

After de-attaching, my reading progress was lost. Not immediately, because when I first start up Logos it was correct, and I started reading from the suggested place. I only discovered the reading progress was lost when I got to the end of my reading, and the "Stop Reading" bar wasn't there.

Andrew Batishko

https://community.logos.com/discussion/comment/886207#Comment_886207

I'm unable to recreate the crash. Are you able to duplicate it? If so, a screen capture of your process might help me recreate your steps.

I was able to duplicate the loss of reading progress when using the "Disconnect" option. This doesn't surprise me, as this disconnects you from the shared document (leaving it in place for others), and in order to do this, it needs to create a new copy of the document for you, which would cause a loss of the associated reading progress data.

This functionality is available in the application using the Groups tool.