Usenet gateway

THIS THREAD IS CLOSED!
Posts in here will NOT be answered

This hack has undergone many major changes since this thread was started. Consequently, most of the posts have become dated and of little use. To coincide with the latest major release (20010712), a new one has been started.

See this thread for the latest version and discussion

[Mark Hewitt]

Originally posted by fastforward
What code changes did you make?

I implemented all the code changes you specified.

Did you go through and re-check the tables to make sure all columns and indexes are as specified in the new versions.

Yes, I deleted all my current usenet forums and removed the usenet_ tables. I then made sure the extra feilds matched up. Think it was only regpost I needed to add. I then created and populated the new usenet tables.

Also, did you make sure you removed any existing code changes you may have made?

I implemented it from a clean copy of RC2 which I was previously running the last version of the hack on.

Hate to heap more problems on you but the NNTP posting time option doesn't seem to work, still uses local time.

Apart from that it works a treat

[fastforward]

I'm working on it. I'll get back to you.

If only there were no users. life would be so much easier for developers

[Mark Hewitt]

If only there were no users. life would be so much easier for developers

I hear ya. Especially ones that don't know how to run a Java class (long story)

[fastforward]

OK...

The parse errors may have been because it was the first time the script was run. The way it works now is it appends any usenet variables that need to be referenced by vB to the 'options' template. This means they can be accessible through layout templates without code changes. The variables causing problems are the post counts which were not quoted. If these are NULL, then it will generate a parse error as the resulting code would like this: ' $usenettotalthreads= ' instead of ' $usenettotalthreads="" '. That's easy to fix.

I can not reproduce your time problem. When I set NNTP in the options all my times show up correctly as the original posting date. Can you reconfirm that this is happening by comparing it against your newsreader? Or have you already done that?

[Mark Hewitt]

The parse errors may have been because it was the first time the script was run. The way it works now is it appends any usenet variables that need to be referenced by vB to the 'options' template.

This sounds about right, especially as everything was restored when I resubmitted the options. However I did run the script twice and the same problem happend both times.

I can not reproduce your time problem. When I set NNTP in the options all my times show up correctly as the original posting date. Can you reconfirm that this is happening by comparing it against your newsreader? Or have you already done that? [/B]

Looking back on it, it's possible the option wasn't set on the second time I ran it. As half the posts seem to be okay. So ignore that part

[fastforward]

A few bugfixes and the addition of the 'exclude usenet posts from new post search' option.

Take note of item number 4. If you have already installed the last version, you MUST change this column type to SIGNED for correct handling of outgoing posts.

1. Added option to exclude usenet posts from 'Get New Posts' search.
2. Fixed bug causing parse errors during first run.
3. Fixed bug causing newnews.pl errors 'e.field invalid column' error if custom profile field for outgoing email isn't added.
4. Fixed incorrect column type for isusenetpost in post and thread tables. They should be TINYINT(2) SIGNED.

This should be one step closer to a bugfree version. Time is running out, vB 2.0 will be out any day

I'll delay the move to vbulletin.org until the final release.

Download latest version

[Mark Hewitt]

Originally posted by fastforward
[B][*]Fixed bug causing parse errors during first run.

I'm still getting the same errors after a run that I detailed above

[Mark Hewitt]

I've looked at the options template and after it has just run it has

$totalusenetposts=5902;
$totalusenetthreads=18;

After I go back and resumit the vB options page is changes to

$totalusenetposts="5902";
$totalusenetthreads="18";

i.e. it now has quotes

For temporary fix I've commented out generateoptions(); as I don't use total threads/posts anyway, and now all seems well.

(another edit). The NNTP post time seems to work for the first few posts then gives up and goes back to local time.

[fastforward]

I think caching causes problems for this template update function aswell. I think the best solution will be if I remove it for the threadcounts and you will have to make a code edit to use them. It's only a one liner anyway.

I still can't reproduce your posting date problem. It's actually only 1 little line in the script that decides the date. When the script starts up, it reads all the config from the tables and then when it gets to the load forums bit it checks to see whether it should replace the nntp date with the local date. So the default is actually NNTP date. I'll keep trying to reproduce it though.

[fastforward]

I've just looked at the code and the quotes are gone again! I think this because I started making the the edits on my test board while at work and then not transfer them to the distribution copy when I got home. All the other fixes I mentioned were still there, it's just the quuote issue around the post counts (which I'm removing anyway).