Need help. Twice I've dragged an image from media into my Sermon notes - it's given me the green plus sign - I let go and my entire sermon notes disappear. I've tried closing the document, closing and reopening the program, and I can't figure out any way to get my sermon notes back. If I go to export them, I can print the text - but it's not rendering on my screen. Is there any way to get my sermon prep back? It's painful to lose my sermon prep after several hours from trying to drag an image into the sermon.

  2. For those who come across this and have a similar experience - I connected with Faithlife support over the phone and they remoted into my computer. Here's what they did as an FYI: 1. Export the blank sermon file to Word or similar file. (You'll have to copy and paste this back into a new sermon document in Logos, so try to save it to as "rich" an option as possible.") 2. Close Logos. 3. Go into Logos folders and rename the Sermon folder - can be as simple as adding the number "1" to the folder name. (When you relaunch Logos and Logos doesn't find this folder, it is going to create a new one and pull data from the cloud to rebuild that folder). 4. Open Logos. Logos will rebuild the sermon folder from what was synced to the cloud. Logos will now sync as it is intended to. The last step is to create a new sermon document, copy and paste the sermon from your Word document into Logos and reformat and relink the elements. In my case, I used what was there to remind my quotes and my notes and re-added those to the sermon brand new so that Logos recreated the slides for me. Hope this might be helpful to someone while the team at Faithlife work on getting the media drag and drop working!

  3. Our development work on this has been completed and the fix will be included on the upcoming 25.0 version. Therefore, I still don't recommend trying this action quite yet, but once you see the 25.0 version, the drag/drop action from the Media tool into Sermon Builder will work as expected. Thanks again to everyone here who helped point this out and gave such helpful information to point our development team in the right direction quickly to implement the patch on this bug.

  4. That’s great! Huge thanks for the team for getting this working!