Duplicate Collections - yet again
Open Beta 8 and find the usual array of duplicated/triplicated Collections.
Bible Topics is a PRA but the flag was not ticked in dupes (2) & (4)
Dave
===
Windows 11 & Android 13
Comments
-
Dave,
I'll add this to the previous report submitted on the Cited By 'All but Bibles' duplication.
Thanks,
Melissa0 -
Ta!
Dave
===Windows 11 & Android 13
0 -
My Apologetics collection was duplicated on my Beta machine, so I deleted the one with the number after it. Now on my non-beta machine I have no Apologetics collection...
0 -
Welcome to Beta 9 - more duplicates
That was horrible to sort as some dupes were PRA's when I wanted them to be and one non-dupe was a PRA when It wasn't previously (I keep a manual record of my collections!).
Dave
===Windows 11 & Android 13
0 -
John Fidel said:
My Apologetics collection was duplicated on my Beta machine, so I deleted the one with the number after it. Now on my non-beta machine I have no Apologetics collection...
I will report this, is one of the collections present in the beta machine? Can you duplicate it and then see if it your main installation will sync with it?
0 -
Dave Hooton said:
Welcome to Beta 9 - more duplicates
After fixing those Beta 9 dupes I logged onto Laptop 4.0a and found a number (7) of missing Collections
It still shows 8 of 15 collections after indexing and restarting for the latest updates.
EDIT:
This morning I find my Desktop 4.0a also has 8 collections with the difference that it has Media Files & lost Hebrew Bibles compared to the Laptop above. I'll restart and see what is left on 4.0b Beta!
Dave
===Windows 11 & Android 13
0 -
Hi George,
The duplicates are on the beta machine. When I eliminate the duplicates on the beta, the collection is gone in the SR machine. Does this answer your question. I have also lost Ancient Texts on the SR Machine. The problem appears to be the top collection that is disappearing in the SR machine. I will recreate the apologetics collection and see later what happens on my beta machine.
0 -
I have seen these duplications reappear for at least the last two betas (8 & 9). Someone's keeping track because I had an 'Utley (20)' collection show up this time.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
I just removed one of the duplicates through the non-beta installation and it deleted both copies.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Stranger yet, after deleting that duplicate, most of the other duplicated collections have now disappeared from my drop down list (non-beta version). They were there a minute ago, but not now. (The originals, thankfully, are still around, unlike the one I intentionally deleted).
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
The duplicates are being created because you are syncing items between two different versions of the app and the resource collection schema was upgraded in 4.0b to support parallel resource associations. You will not see the duplicate on the 4.0a instance as schema version of the other copy is not supported.
There are some bugs in the Collections UI which cause resource collections to be synced unnecessarily, (a side-effect of opening the UI) which exacerbates the issue. We'll be addressing these before the next beta.
0 -
Scott Alexander said:
There are some bugs in the Collections UI which cause resource collections to be synced unnecessarily, (a side-effect of opening the UI) which exacerbates the issue. We'll be addressing these before the next beta.
Thanks for that. But can you account for the deleted Collections in 4.0a?
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Thanks for that. But can you account for the deleted Collections in 4.0a?
Setup - Machine A running Logos 4.0a, machine B running Logos 4.0b, both have collection Foo
- Machine B - Collections UI is opened and Foo is automatically (due to a bug) marked as edited and synced
- Machine A - syncs changes made by machine B but ignores them due to newer schema version
- Machine A - edits its own copy of Foo and syncs, causing a conflict to be generated on the server. Note you will never see the copy with the newer version on machine A. After this sync the collection Foo should have been renamed Foo (1) indicating it generated a conflict (bug).
- Machine B - syncs and sees Foo (1) generated by machine A which looks like a dupe and is deleted. The user is actually deleting the only version accessible by machine A
- Machine A - syncs and Foo collection is removed
The bugs mentioned in steps 1 and 3 have been fixed for Beta 10
0 -
Scott Alexander said:
The bugs mentioned in steps 1 and 3 have been fixed for Beta 10
Scott,
Great! Seems we have finally found the root causes.
I haven't replaced the missing collections in 4.0a and the collections in 4.0b are complete. Is there anything you want me to check in Beta 10?
Dave
===Windows 11 & Android 13
0 -
Scott Alexander said:
The bugs mentioned in steps 1 and 3 have been fixed for Beta 10
I got one dupe (expected) from 4.0a.
I installed Beta 11 on my new desktop and all collections were present ie. restored by Sync'ing.
Looking good.
Dave
===Windows 11 & Android 13
0 -
I have now got two installations on B12 and the duplicate issue appears to be under control!
Good work Scott.
Dave
===Windows 11 & Android 13
0
