new nzb system

[eyekey]

doesn't work for Windows 7 w/ newsbin pro 5.52/firefox

just dowloads the nzb and does not open :ermm:

[Skiz]

Ditto. It's creating a file with an .nzb extension but it doesn't seem to be an actual NZB as no client recognizes it. :unsure:

[tesco]

Some bugs were found with this and i've changed us back to the old system until I can find and fix all of the bugs. :(

[Skiz]

The old look is back, but it's still spitting out bad nzbs.

[tesco]

It took me an hour to track down but I think i've finally fixed this issue.
The new system is back up now.
Please let me know.

I've only tested these nzbs with newsleecher. Not sure how other newsreaders like them. :unsure: Going to try a few now.

edit: Works fine in GrabIt.

edit2: And alt.binz

[Skiz]

Works for me. :)

Also, I was thinking that it would be better to have everything already selected and let users deselect anything they don't want. I'd think that most people who are downloading are going to choose select all, so this would just be a bit easier imo.

[tesco]

That's a good point.
I'll work on that tomorrow. :)

[tmas3]

Just noticed the change a few minute. Went to test it out and sure enough newsbin pro no longer opens the nzb. I never had a problem with the old system that only downloaded zips. I cant get anything to work with the new system. Please fix!!

NewsBin Pro 5.35 and FireFox

[Skiz]

Just noticed the change a few minute. Went to test it out and sure enough newsbin pro no longer opens the nzb. I never had a problem with the old system that only downloaded zips. I cant get anything to work with the new system. Please fix!!

NewsBin Pro 5.35 and FireFox

Works fine for me. I did have to reassociate NZBs to my client for some reason, but everything works fine.

[tmas3]

nope still broken. It downloads the nzb fine but it wont load anything into newsbin now. Hopefully this problem is fixed for everyone so I dont have to leave the forum

EDIT: binsearch still creates nzbs that open in newsbin so its obviously something changed with the new format

[tesco]

This program seems to be very strict about how the NZBs are constructed.
Which is good I guess, it helps to iron out any bugs. :)
I made a couple of tweaks to how the system creates it's NZBs.

The NZBs should be importing fine to NewsBin Pro (tested with 5.52).

[tmas3]

Works now thanks! :)

[tesco]

As usual if you find any more bugs let me know :)



Also, I was thinking that it would be better to have everything already selected and let users deselect anything they don't want. I'd think that most people who are downloading are going to choose select all, so this would just be a bit easier imo.
Done.

Any more suggestions just let me know. :)

[SonsOfLiberty]

Alright, damn it, what's the file size restrictions for a NZB?

The one I have is 6 movies into one at 13mb, so I've zipped it to 661kb, but the system, on any browser goes to this: http://filesharingtalk.com/vb3/newthread.php with no new thread. On either NZB I try to upload.

[tesco]

Attach the NZB here so I can test it.
Theoretically it should be unlimited size other than the fact that you can only upload a 24mb rar, but that can fit a hugeeeee nzb so you should never hit the limit.
Might just be running out of memory. Maybe I'll have to make the NZB system deal with only chunks of the file at a time. :unsure:

[SonsOfLiberty]

Doing now, here's both.... this one took me a week...and finally it worked..the uncompressed one was over 5mb and the compressed one was under 1mb but kept doing the new thread error.

http://filesharingtalk.com/vb3/f-movie-nzbs-80/t-star-trek-i-vi-brrip-xvid-ac3-flawl3ss-351236

But it seems like anything over 4mb's sometimes I get that error sometimes I don't get that error.

Attach max size for NZB says 5mb, here's the uncompressed, uploading the uncompressed NZB's gives me: I've exceeded the limit of 5mb's NZB :lol:

Check shit.png :)

[tesco]

Thanks, I'll try that one out and use it for my testing. :)

So eventually you were able to get it to go through but it took many tries, is that what you're saying?

And as for the attachment limit yes it's 5mb for NZBs and I think 10mb for rars/zips, but that does not affect NZBs uploaded through the Submit NZB because they're stored in a completely different place.

[SonsOfLiberty]

I would always get the new thread error if the NZB was above 5mb..even when I compressed it, it still threw me errors, and just one day the compressed NZB of star trek went through...but since then I've tried others and I get blank pages and Opera says the that there is no connection to FST...and FF just blank pages me. I've tried that Star Wars compressed NZB over 10 times and the uncompressed the same and the same results, even with only one tab open and nothing else running or downloading or uploading.

[tesco]

Upping the memory limit solved the problem. It goes right through now.
Not sure if this will have any consequences. :unsure:

[SonsOfLiberty]

I'll post it now and post back. Worked, the compressed one went right through.

[SonsOfLiberty]

I upped another NZB (Star Trek Voyager S07 COMPLETE DVDR-Anonymous)and it went to the new thread page again, only 5mb NZB, so I compressed it and went through, but when I went to the index it was this, but no age stamp (where it shows how old)...I moved the un-day-stamped one to the trash, so if you wanna look it's there.

Also, when we import the NZB, can it automatically add that to the release name? So we don't have to name it, it will just grab the name of the NZB, but users can still have the choice to name it whatever they want?

[SonsOfLiberty]

It did it again, this time no new thread, but look it shows a blank on the main page, and no thread in the movie index. NZB was only 3MB....maybe it has something to due with NFO fetching?

[shiny69]

Hi guys, dont know if its just me but I cannot see any .nzb links to d/l on the pages anymore....they where there last night....now they aint..:(....help..

[SonsOfLiberty]

yeah I can't either, some bug, screeny's.

Plus tons of no permission's as well

[Mpeace]

Must be a new issue...

[tesco]

The nzb issue is fixed. Was reality's fault he made a change to a plugin and it wrote the code wrong and it screwed up every plugin related to how posts are displayed.

As for that permission error maybe reality removed you from the Trusted Community. :P

[Mpeace]

Ty tesco for the quick response

[shiny69]

Nice one guys, thanks

[SonsOfLiberty]

Whenever you NUKE a NZB now you can't see the reason, it's invisible, well you can kind of see but not unless you look really really hard and it's in white :lol:

[Hairbautt]

Is it just me or does the NZB index no longer reflect viewed or previously 'read' NZB threads?

Nevermind. I think it was because I got logged out somehow. Didn't notice since the board stayed to the vbulletins 3 colors style.

[SonsOfLiberty]

Oh tesco..this is what I mean by age stamp missing...along witht the post saying 0 MB, but also, at the bottom of the post, it says the real size, screeny's yo.

Also the NUKE thing on the previous page too

[tesco]

okay the problem is with uploading nzbs that contain just 1 file.
I'll fix it later.

[prologix]

I dunno if it's a bug or what but I'm seeing lots of nzb's that are incomplete and missing lots of files.

[tesco]

Links please.

[SonsOfLiberty]

I notice that too, every now and then, Newsleecher and Binsearch, etc...won't give you all the NZB files for some odd reason, and there's been times where I've had full NZB's and posted them here and then I see missing files.....theres some in the trash.

[Skiz]

The Thanks button is pretty hidden now.

I'd suggest placing a new matching button to the right of "Create .NZB.ZIP". :unsure:

[SonsOfLiberty]

Is there any function to update an NZB that is currently in a post? Without moving it to the trash and re doing another post, in case it's missing PARS or the like?

[Skiz]

I just go to advanced edit and attach the pars.

[tesco]

Is there any function to update an NZB that is currently in a post? Without moving it to the trash and re doing another post, in case it's missing PARS or the like?
Not yet; that's in the near future though.

[SonsOfLiberty]

one other that would be nice, say you post a NZB then you have another, instead of going all the way back to the index, could we get a button inside all threads that say submit NZB? For example if this gets posted then have a add button inside of there, hopefully I'm making sense.

[tesco]

one other that would be nice, say you post a NZB then you have another, instead of going all the way back to the index, could we get a button inside all threads that say submit NZB? For example if this gets posted then have a add button inside of there, hopefully I'm making sense.
Ya makes sense and I think we used to have that a long long time ago.
There was a message: "Your NZB was submitted. Click HERE to post another."

[SonsOfLiberty]

Not now, I double checked it...didn't see that anywhere...or submit anywhere inside of the thread.

[tesco]

Not now, I double checked it...didn't see that anywhere...or submit anywhere inside of the thread.
We don't have it now.
Was just saying that we used to.

[SonsOfLiberty]

Edit

[tesco]

Now, if I grab just a NZB from a group and upload it it's reported 01/131 on all parts.

Is that reading fine?

i've had numerous reports from users saying that there fucked up.

But if you look at a movie NZB, and looks at the post it will say (example) 68/68 or 123/123, etc, etc....I downloaded NZB's fine that I posted but I don't have a clue.....please explain :lol:

Example,

1st post is just the NZB grabbed from efnet and the post all kinds of screwy
http://filesharingtalk.com/vb3/f-tv-nzbs-120/t-masterchef-australia-s01e61-ws-pdtv-xvid-rta-358283

Now on this one, I combined all posts including the NZB and 'exported' to NZB and look, all parts are showing full
http://filesharingtalk.com/vb3/f-tv-nzbs-120/t-man-moon-ws-pdtv-xvid-waters-358284

I noticed that problem (which wasn't one before) goes back more than 12 days.

In fact I know it's a FST bug, because I post the exact "SAME" NZB's at another forum and it shows all parts complete

I can tell you this, I won't be posting anymore TV if I have to cull every post and export to NZB that takes ages, oh and I just culled some posts from the TV index, it's not just mine either, other posters are grabbing teh NZB from different sources "i presume" #abmm and there posts are showing exactly the same as mine 01/xxx
SOL, can you please send me an NZB file that has this bug?
Not sure I understand how it's occuring.
Are you saying you upload it here, it's fine, then download it from here, then reupload it here and it's no longer good?:wacko:

Please just send me one NZB with this problem when you upload it, along with where you got it from, and I'll definately take a look at this asap.


===

Not sure I even see any problem at all. I just downloaded an NZB from the first thread you linked to and it downloaded fine... :blink:

[SonsOfLiberty]

Bah, never mind :lol:

[SonsOfLiberty]

I guess Binsearch shows the same....1/39, wonder why if you export it to a NZB it will show up 39/39 as oppossed to NZB only it will shows 1/39

But NewzLeech doesn't:

http://newzleech.com/?p=6622188

[tesco]

Okay I just looked at a couple of NZBs you posted in that thread.

I'm looking at these:

Krod.Mandoon.S01E06.EXTENDED.HDTV.XviD-BiA.nzb
Krod.Mandoon.S01E06.EXTENDED.HDTV.XviD-BiA-EXPORTED.nzb

The first one (NZB created by efnet?) is the broken one.
Here shows an example of the difference between the two.

Looking at this file as an example:
"#a.b.mm@efnet - req 83972 - Krod.Mandoon.S01E06.EXTENDED.HDTV.XviD-BiA - [15/25] - "krod.mandoon.s01e06.extended.hdtv-bia.r12" yEnc (01/39)"

In the efnet nzb:

<file poster="[email protected]" date="1246917273" subject="#a.b.mm@efnet - req 83972 - Krod.Mandoon.S01E06.EXTENDED.HDTV.XviD-BiA - [15/25] - "krod.mandoon.s01e06.extended.hdtv-bia.r12" yEnc (01/39)">
<groups>
<group>alt.binaries.multimedia</group>
<group>alt.binaries.tv</group>
</groups>
<segments>
<segment bytes="398296" number="1">[email protected]</segment>
<segment bytes="398422" number="2">[email protected]</segment>
<segment bytes="398231" number="3">[email protected]</segment>
<segment bytes="398247" number="4">[email protected]</segment>
<segment bytes="398165" number="5">[email protected]</segment>
<segment bytes="398285" number="6">[email protected]</segment>
<segment bytes="398432" number="7">[email protected]</segment>
<segment bytes="397981" number="8">[email protected]</segment>
<segment bytes="398124" number="9">[email protected]</segment>
<segment bytes="398305" number="10">[email protected]</segment>
<segment bytes="398177" number="11">[email protected]</segment>
<segment bytes="398008" number="12">[email protected]</segment>
<segment bytes="398060" number="13">[email protected]</segment>
<segment bytes="398242" number="14">[email protected]</segment>
<segment bytes="398382" number="15">[email protected]</segment>
<segment bytes="398518" number="16">[email protected]</segment>
<segment bytes="398151" number="17">[email protected]</segment>
<segment bytes="398040" number="18">[email protected]</segment>
<segment bytes="398285" number="19">[email protected]</segment>
<segment bytes="398295" number="20">[email protected]</segment>
<segment bytes="398122" number="21">[email protected]</segment>
<segment bytes="397963" number="22">[email protected]</segment>
<segment bytes="398152" number="23">[email protected]</segment>
<segment bytes="398349" number="24">[email protected]</segment>
<segment bytes="398431" number="25">[email protected]</segment>
<segment bytes="397898" number="26">[email protected]</segment>
<segment bytes="398068" number="27">[email protected]</segment>
<segment bytes="398345" number="28">[email protected]</segment>
<segment bytes="398127" number="29">[email protected]</segment>
<segment bytes="398444" number="30">[email protected]</segment>
<segment bytes="398472" number="31">[email protected]</segment>
<segment bytes="398257" number="32">[email protected]</segment>
<segment bytes="398336" number="33">[email protected]</segment>
<segment bytes="398611" number="34">[email protected]</segment>
<segment bytes="398064" number="35">[email protected]</segment>
<segment bytes="398537" number="36">[email protected]</segment>
<segment bytes="398483" number="37">[email protected]</segment>
<segment bytes="398474" number="38">[email protected]</segment>
<segment bytes="342324" number="39">[email protected]</segment>
</segments>
</file>And in the EXPORTED NZB:


<file subject="#a.b.mm@efnet - req 83972 - krod.mandoon.s01e06.extended.hdtv.xvid-bia - - &quot;krod.mandoon.s01e06.extended.hdtv-bia.r12&quot; (39/39)" date="1246924452" poster="[email protected]">
<groups><group>alt.binaries.tv</group></groups>
<segments>
<segment number="1" bytes="397312">[email protected]</segment>
<segment number="2" bytes="397312">[email protected]</segment>
<segment number="3" bytes="397312">[email protected]</segment>
<segment number="4" bytes="397312">[email protected]</segment>
<segment number="5" bytes="397312">[email protected]</segment>
<segment number="6" bytes="397312">[email protected]</segment>
<segment number="7" bytes="397312">[email protected]</segment>
<segment number="8" bytes="397312">[email protected]</segment>
<segment number="9" bytes="397312">[email protected]</segment>
<segment number="10" bytes="397312">[email protected]</segment>
<segment number="11" bytes="397312">[email protected]</segment>
<segment number="12" bytes="397312">[email protected]</segment>
<segment number="13" bytes="397312">[email protected]</segment>
<segment number="14" bytes="397312">[email protected]</segment>
<segment number="15" bytes="397312">[email protected]</segment>
<segment number="16" bytes="397312">[email protected]</segment>
<segment number="17" bytes="397312">[email protected]</segment>
<segment number="18" bytes="397312">[email protected]</segment>
<segment number="19" bytes="397312">[email protected]</segment>
<segment number="20" bytes="397312">[email protected]</segment>
<segment number="21" bytes="397312">[email protected]</segment>
<segment number="22" bytes="397312">[email protected]</segment>
<segment number="23" bytes="397312">[email protected]</segment>
<segment number="24" bytes="397312">[email protected]</segment>
<segment number="25" bytes="397312">[email protected]</segment>
<segment number="26" bytes="397312">[email protected]</segment>
<segment number="27" bytes="397312">[email protected]</segment>
<segment number="28" bytes="397312">[email protected]</segment>
<segment number="29" bytes="397312">[email protected]</segment>
<segment number="30" bytes="397312">[email protected]</segment>
<segment number="31" bytes="397312">[email protected]</segment>
<segment number="32" bytes="397312">[email protected]</segment>
<segment number="33" bytes="397312">[email protected]</segment>
<segment number="34" bytes="397312">[email protected]</segment>
<segment number="35" bytes="397312">[email protected]</segment>
<segment number="36" bytes="397312">[email protected]</segment>
<segment number="37" bytes="397312">[email protected]</segment>
<segment number="38" bytes="397312">[email protected]</segment>
<segment number="39" bytes="397312">[email protected]</segment>
</segments>
</file>
This proves there's a problem with the NZB file and not with how FST handles them.
Not sure what to tell you...


I guess Binsearch shows the same....1/39, wonder why if you export it to a NZB it will show up 39/39 as oppossed to NZB only it will shows 1/39

But NewzLeech doesn't:

http://newzleech.com/?p=6622188
Those efnet NZBs are automatically generated, possibly too early (before the files are fully uploaded).
Not sure where they're pulling those incorrect messageIDs from though.

[SonsOfLiberty]

So what I'm getting ad to the downloads still work with the "broken" ones from efnet?

Edit, today, yes they do