It brings me to : http://www.mysite.nl/forum/Warn.php?do=ViewMyWarnings But with the url which you gave me.

PLEASE DO NOT USE THE AUTOMATIC WARNING FEATURE OF THIS HACK.

I have discovered a bug, where the automatic warning is attributed not to the post that issued it, but to the post before it.

I am working on the solution, but until I have everything finalize, please turn off the Automatic Warnings for posts.

Thank you and I am sorry for the inconvenience.

Version 3.0.7 was just uploaded, which corrects the bug in the Automatic Warnings for posts.

The bug affected only replies posted in a thread, not the first post in a thread, or edits done to an existing post.

For those who have "ObsceneWords"-type of warnings in your forum, I think you should check them out. I had only 3 of them, and the one was the first in a thread, so it was not affected. The rest were fixed easily with a little investigating work in the post table and a few SQL commands.

Gentlemen, I am really sorry for any inconvenience I caused you.

:-(

sql syntax help please

ALTER TABLE `".TABLE_PREFIX."post` ADD COLUMN `warn_flag` int(5) default 0 AFTER attach

my prefix is vb3 but

i thought it would be like this:
ALTER TABLE vb3_post ADD COLUMN `warn_flag` int(5) default 0 AFTER attach

but i keep getting a syntax error
MySQL said:


You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'default0 AFTER attach' at line 1

please help

That's strange. Warn.php takes you to "ViewMyWarnings" if it doesn't find any other "do" directive. OK, let's try this:

Let me know where that takes you.

Rgds

Dangit, John! What do you think we're paying you all that good money for! ;) lol

Thanks for all of your hard work. I'll be upgrading tonight. :)

Torqued,

I feel really sorry. I have done tests on tests and more tests on anything, and this slipped my attention. I guess I can blame vB a little, because somwhere above my code, it calls a function, with the parameter $_POST['postid'], so I assumed (without checking, the idiot), that that parameter was the postid of the new reply. However, this was not the case, this is the id of the previous post in the thread, and is used inside the called function to link the posts together. It is inside that function that the new reply's id is generated.

So I goofed big time!

At least I had the fix out within one hour I noticed the problem.

Time to go to bed, it's 2:30 am here.

Rgds

oh please oh please help me with my syntax error b4 you do go to bed.
i'm not sql guy
thanks in advance

You have not left a space between the word "default" and the zero. I think this is your error. Is it?

I'll wait for you to tell me. I'll have another cigarette.

Rgds

i tired this:
ALTER TABLE vb3_post ADD COLUMN `warn_flag` int(5) default 0 AFTER attach

and got this:
Error

SQL-query :

ALTER TABLE vb3_post ADD COLUMN `warn_flag` int( 5 ) default 0 AFTER attach

MySQL said:

You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'default0 AFTER attach' at line 1

there is a space between default and 0