Collections Out of Control..
I am not sure what is going on or what I have done wrong but my Unnamed Collections are growing like the Blob from the 1970's movie.. Even when I try and delete them and get back to just the default one they all pop back in place and then create another one..
Comments
-
I've just checked and not seeing this.
Every time you click "New" in the Collections Tool you will get another "Unnamed Collection" but you should be able to delete them and for them to stay deleted.
Are you clicking the "New" button much?
0 -
There was a problem similar to this a few years ago which Logos fixed. I don't recall the details, but like you, I had mysteriously replicating collections. It had something to do with their syncing of our collections from their server. It didn't effect everyone.
Hopefully someone from Faithlife will see this thread and look into the problem.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
That is what is odd.. I have tried to delete them several different times(In different orders and such) and they always snap back in and then name a new Unnamed collection incrementing the number.. Being a System Analyst/Programmer by trade, it seems the program is keeping track of the Unnamed Collections and how many there are in the code and doing(Or not doing) something with it..
Kind of driving me crazy as no matter what I do to try to fix it, it just keeps growing.. Maybe I should stop messing with it..[:|]
0 -
I delete them all(But leave the default one without the () number) Run the Sync Now, Close the whole program then start it back up and go to collections and bam it defaults to Unnamed Collection(18) and all the ones I deleted are back.. [:'(]
0 -
Interesting.. I tried renaming them all to something else with a unique name to get them out of the array ()... For example like Unnamed Collection(14) to Rodney 14.
And well that did the trick BUT now when I go in and try and Deleted all my Rodney 1 -18 they Snap back in and I can't delete them.. Something definitely programmatic going on..
Hopefully Someone from FaithLife will be able to tell me what to do to clean this all up..
0 -
Yep. Be glad it is only happening to one collection. I don't know of anything you can do to fix the problem. I suggest you leave it and go on to something else. If no one from FL looks in, you can call or email support for help.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Just an Idea. Can you delete this unnamed Collection on your Logos Account? Under Dokuments.
Sascha
0 -
Will take a look into that Sascha
Thanks Guys..
0 -
Rodney Phillips said:
Interesting.. I tried renaming them all to something else with a unique name to get them out of the array ()... For example like Unnamed Collection(14) to Rodney 14.
And well that did the trick BUT now when I go in and try and Deleted all my Rodney 1 -18 they Snap back in and I can't delete them.. Something definitely programmatic going on..
Hopefully Someone from FaithLife will be able to tell me what to do to clean this all up..
If I remember correctly, this was sometimes caused when more than one instance of Logos was open at the same time (desktop and/or laptop with tablet or smart phone). Could that be the case here?
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
No.. I don't believe so..
0 -
Everytime I open Collections I don't even hit new or anything and it creates a new Unnamed Collection. This has to be a bug?
Now back up to Unnamed Collection(8). Just from Opening Collections
And still have all the Rodney 1 thru 14 I cant delete..
0 -
Just got off phone with Tech Support and he was able to duplicate this issue on his end and is turning it over to the Developers.. Very nice guy..
Glad I am not going crazy like I first thought.. [H]
0 -
It's the same Probleme now here with me :-(
0 -
Yea.. He said it looked like a Syncing issue where deleted items get synced right back in..
0 -
dit he also say what to do?
0 -
Sascha John said:
dit he also say what to do?
He passed the case on to the developers (programmers) as he was unable to fix it. So we await word from Faithlife about this issue. Until then we (or at least those affected) will have to live with the inconvenience.
Hopefully this will get rapid attention.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
OK thanks :-)
Sascha
0 -
What Mark said.. [8-|]
0 -
Just wanted to say, Me too. Which is how I found this. Deleted the collections, ahhh, problem solved. BAM! right back again.
Will be glad when it's fixed. Thanks for bringing it up and pursuing it.
Win10 home; 32GB RAM; i7 - 10700 CPU @ 3. 80 GHz (10th gen, 8 cores); GTX 950 Video Card (2GB); SSD
0 -
I had to test it and now it's doing the exact same thing to me. When it syncs the unnamed collections reappear.
0 -
I'm having the same issue. I called tech support about it and he directed to the documents.logos.com page and suggested I delete from there. I did and nothing happened. All my "unnamed collections" are snapping back as well. Here's what I did which might suggest a sync problem. I turn off my internet connection and was able to delete my collections without them coming back. But as soon as I connected they reappeared. It's driving me bonkers. But like rest of you guys I guess I'll have to wait and see what they do.
0 -
A server-side fix for this issue was just deployed.
After deleting a collection locally, to test the fix, it looks like all of my previously deleted collections are now also gone.
0 -
Terrific! I'll look forward to bidding a tearful farewell to Unnamed Collections 1-479! (Slight exaggeration)
Win10 home; 32GB RAM; i7 - 10700 CPU @ 3. 80 GHz (10th gen, 8 cores); GTX 950 Video Card (2GB); SSD
0 -
Hi. So far so good. I deleted all the "unnamed collections" along with the others and they are not reappearing or "snapping back". God bless to the people who created the fix. Sanity returns.
0 -
Jacob, (please don't hit me,..) but I think there may be corruption in the cloud (praying not but..) (my logic is: my layouts have just had 3 Dutch named layouts added) and although I know a little Dutch they are not mine, based on my experience these collections may actually belong to another user entirely.. it appears your fix has worked for these collections tho - thx
Never Deprive Anyone of Hope.. It Might Be ALL They Have
0 -
It seems to have worked for me. Thanks!
0 -
Excellent.. Thanks Faithlife for the super fast fix..
0 -
Mine also appears to be fixed! Thanks!
Win10 home; 32GB RAM; i7 - 10700 CPU @ 3. 80 GHz (10th gen, 8 cores); GTX 950 Video Card (2GB); SSD
0
