BUG: Reinstalling L4...Collections do not sync

I'm running Logos Bible Software 4.5 Beta 7 (4.50.0.1444)

This apparently isn't just a BETA issue if you look at this

I had to do a re-install of L4 on my desktop computer. When it was all done (including indexing), I started it up and NONE of my collections were there. Everything else seemed to sync but not my collections! I did this twice...with the same result.

I contacted Logos customer service and was transferred to the tech department, but since it was Beta they couldn't help me. They suggested I switch to a stable release. Well from the post I referenced above, it appears the same problem exists in the stable release, and the only way to remedy it is renaming the collections.

This happened to me once before, just after L4 came out. I had to change the collection titles for them to sync. I had forgotten...until the repetition reminded me.
I just did this again to get them to sync to my new desktop installation again. Only this time I have many more collections and it took me hours to rename them to get them to sync and I still haven't completed renaming them back to their original names.

Please, oh please, get this fixed so when I get my new laptop I will not have to spend the day renaming my collections for them to appear. A new install or re-install should sync everything, not everything but collections!

Find more posts tagged with

Comments

Todd Phillips

Please, oh please, get this fixed so when I get my new laptop I will not have to spend the day renaming my collections for them to appear.

This is a bug that needs to be fixed.

But in the mean time, using method two of the "Quick_Installation_onto_multiple_computers" will move your collections to the new computer (along with the resources and indexes and documents and all other settings). I highly recommend it:

http://wiki.logos.com/Quick_Installation_onto_multiple_computers#Method_2

Tonya J Ross

A new install or re-install should sync everything, not everything but collections!

Agreed.

My response in the other thread you mentioned:
"I'm unsure whether or not the implementation of sync v2 (the new sync framework being written for the program) will resolve the issue once it is applied to Collections. I've reported the issue to Development for investigation."