I know there used to be a option to manually rebuild parts. I am unable to find it. Is this option renamed or removed?
Or is there an other way to combine two threads / collections?
I now have two threads one with 16% of the bodies and another with 83% of the bodies. Combined I would have all the parts.
Manually rebuild parts
do you really mean single parts, like (1/100) and (1/1) to (1/83) you want to merge with (1/84)-(1/100) to achieve a single partial message?
or you mean files (whole partial messages), just they split into two collections but you would prefer to see them under a single collection entry?
collections right now are hard coded and set by the current algorithm, they are not even reflected in the database so i have an option to adjust the algorithm without changing the database structure. manual "forcing" a set of entries into a single collection does make sense, i'm thinking maybe i'll add something like that, but then it will change the database structure (the database structure didn't change since v1.0 but it is not a problem to change it if there is something consistent and meaningful).
as to joining parts, there is such an option in newspro, but with par2 recovery and the trend of shifting to macro level without even mentioning parts i didn't reimplement the manual parts reassembly option, although in UE you can see the parts as the thread under the partial message, do some operations like purge them or e.g. save them into nzb, then import them in newspro and join them there into a single message. but i guess you mean files and collections, not partial and parts?
or you mean files (whole partial messages), just they split into two collections but you would prefer to see them under a single collection entry?
collections right now are hard coded and set by the current algorithm, they are not even reflected in the database so i have an option to adjust the algorithm without changing the database structure. manual "forcing" a set of entries into a single collection does make sense, i'm thinking maybe i'll add something like that, but then it will change the database structure (the database structure didn't change since v1.0 but it is not a problem to change it if there is something consistent and meaningful).
as to joining parts, there is such an option in newspro, but with par2 recovery and the trend of shifting to macro level without even mentioning parts i didn't reimplement the manual parts reassembly option, although in UE you can see the parts as the thread under the partial message, do some operations like purge them or e.g. save them into nzb, then import them in newspro and join them there into a single message. but i guess you mean files and collections, not partial and parts?
I mean files that are split for some reason in two incomplete collections.
A pity I can not put a screen dump in the message. But this is what I mean:
First file with three parts
[Silent_Hunter_4_Wolves_of_the_Pacific_v1.2_Patch-HATRED]-[03/20] - "htd-sh12.r00" y nc (*/24)
[Silent_Hunter_4_Wolves_of_the_Pacific_v1.2_Patch-HATRED]-[03/20] - "htd-sh12.r00" y nc (19/24)
[Silent_Hunter_4_Wolves_of_the_Pacific_v1.2_Patch-HATRED]-[03/20] - "htd-sh12.r00" y nc (20/24)
[Silent_Hunter_4_Wolves_of_the_Pacific_v1.2_Patch-HATRED]-[03/20] - "htd-sh12.r00" y nc (21/24)
Second file with the rest of the parts
[Silent_Hunter_4_Wolves_of_the_Pacific_v1.2_Patch-HATRED]-[03/20] - "htd-sh12.r00" yEnc (*/24)
[Silent_Hunter_4_Wolves_of_the_Pacific_v1.2_Patch-HATRED]-[03/20] - "htd-sh12.r00" yEnc (1/24)
[Silent_Hunter_4_Wolves_of_the_Pacific_v1.2_Patch-HATRED]-[03/20] - "htd-sh12.r00" yEnc (2/24)
I do not get it why this file is split up in two. If a got the terminology right these files shoul be in the same collection. I will purge the files and to a clean NZB import to see if things improve. But if you use the search function from within usenet you will see the same splitting of files.
But thanks for the quick reply.
A pity I can not put a screen dump in the message. But this is what I mean:
First file with three parts
[Silent_Hunter_4_Wolves_of_the_Pacific_v1.2_Patch-HATRED]-[03/20] - "htd-sh12.r00" y nc (*/24)
[Silent_Hunter_4_Wolves_of_the_Pacific_v1.2_Patch-HATRED]-[03/20] - "htd-sh12.r00" y nc (19/24)
[Silent_Hunter_4_Wolves_of_the_Pacific_v1.2_Patch-HATRED]-[03/20] - "htd-sh12.r00" y nc (20/24)
[Silent_Hunter_4_Wolves_of_the_Pacific_v1.2_Patch-HATRED]-[03/20] - "htd-sh12.r00" y nc (21/24)
Second file with the rest of the parts
[Silent_Hunter_4_Wolves_of_the_Pacific_v1.2_Patch-HATRED]-[03/20] - "htd-sh12.r00" yEnc (*/24)
[Silent_Hunter_4_Wolves_of_the_Pacific_v1.2_Patch-HATRED]-[03/20] - "htd-sh12.r00" yEnc (1/24)
[Silent_Hunter_4_Wolves_of_the_Pacific_v1.2_Patch-HATRED]-[03/20] - "htd-sh12.r00" yEnc (2/24)
I do not get it why this file is split up in two. If a got the terminology right these files shoul be in the same collection. I will purge the files and to a clean NZB import to see if things improve. But if you use the search function from within usenet you will see the same splitting of files.
But thanks for the quick reply.
yes you can purge parts and then import the nzb file if it is supplied otherwise you can export the partial into nzb file, edit the subject there, purge the partial or parts from the header list and then import the nzb file. just the current subject of the loaded header prevails so if you load nzb with different subject but the same message-ids and the message-ids are already loaded with a different subject - nothing will change.