The SQL Queries... for the Upgrade Instructions

[Blootix]

When I executed that:

RENAME TABLE `".TABLE_PREFIX."warning_options` TO `".TABLE_PREFIX."NOT_USED_warning_options`

They gave me an error message of some sort, but quickly redirected the screen. It was some sort of Warning Error in db_mysql.php. The table was renamed though.

When I executed:
DROP TABLE `".TABLE_PREFIX."warning_options`
there was:
An error occurred while attempting to execute your query. The following information was returned.
error number: 1051
error desc: Unknown table 'vb3_warning_options'
I think we're supposed to do:

DROP TABLE '".TABLE_PREFIX."NOT_USED_warning_options'

Am I right?

Also, one more problem that I just found. If you warn somebody using a ' then it'll come up to be a \' when using the Moderator Comment.

For example, when I post, you'll it comes out to be you\'ll

Another error: there is a parse error in the redirection page when you warn somebody where it says Test User X Has Been Warned, PM-ed and e-mailed. Taking You Back To The Post:
Parse error: parse error, unexpected T_ENCAPSED_AND_WHITESPACE, expecting T_STRING or T_VARIABLE or T_NUM_STRING in /****/**********/public_html/board/includes/functions_warning.php(475) : eval()'d code on line 19

Another error: private messages are not working.

When a user try to send a private message to another user, the content of the private message would be absent. Look at the screenshot for more information.

EDIT: nevermind about the private message. I accidentally deleted the line $message=$pm_message;.

[sv1cec]

You are correct about the table, I 'll correct the instructions.

I thought I had fixed that in the past, but it's not in the file, so you are right. I'll post a new zip file, in a while, dowload it and upload the includes/functions_warning.php file to your server.

The parse error I am not sure where it comes from maybe it is due to the PM problem? At that line, the program should be evaluating warn_pm, so maybe the two are related?

Let me know if you are OK.

[Blootix]

You are correct about the table, I 'll correct the instructions.

I thought I had fixed that in the past, but it's not in the file, so you are right. I'll post a new zip file, in a while, dowload it and upload the includes/functions_warning.php file to your server.

The parse error I am not sure where it comes from maybe it is due to the PM problem? At that line, the program should be evaluating warn_pm, so maybe the two are related?

Let me know if you are OK.
I fixed the PM problem, but the parse error was still there. I even made sure every modification to private.php was correct but the annoying parse error was still there. After I replace the fuctions_warning.php I'll try again.

[sv1cec]

I fixed the PM problem, but the parse error was still there. I even made sure every modification to private.php was correct but the annoying parse error was still there. After I replace the fuctions_warning.php I'll try again.
Use the following as your warn_pm template:


Dear $user[username],

You have been warned for one of your posts, which violated $vboptions Rules. The reason you have been warned is because:

[b] $warn_type[warn_desc]
(Warning Type = $warn_type[warn_name])

For this violation, you have been given : $warn_type[warn_points] point(s).
The point(s) will remain in your account for $warn_type[warn_maturity] days.
After that, they will be removed automatically.

The post for which you are warned can be seen here:

$thread1

The admin/moderator who warned you, entered this comment:

=======================================
$_POST[comment]
=======================================

Your total Warning Level at the moment is: $level point(s).

If you reach the maximum of $vboptions[warn_points_before_banned], you will be banned from the Forums, for $peruserbanlimit days.

To see details about all the warnings you have received, until now, please click here ($vboptions[bburl]/Warn.php?do=ViewMyWarnings).

Please reply back if you have a dispute.


I suspect an error in the warn.xml file, that was used to install the templates.

I also uploaded version 3.3.1 which fixes your apostrophe issues.

Rgds

[Blootix]

One more thing :nervous:

When we use $wcomment in the warn_view_row and warn_viewb_row templates, it doesn't work. The comment field would become blank (see screenshot) even though a Moderator comment was entered. When we use $warn[warned_reason], that "\" thing comes back. :surprised:

Any ideas?

[sv1cec]

One more thing :nervous:

When we use $wcomment in the warn_view_row and warn_viewb_row templates, it doesn't work. The comment field would become blank (see screenshot) even though a Moderator comment was entered. When we use $warn[warned_reason], that "\" thing comes back. :surprised:

Any ideas?
Did you uploaded the new files from release 3.3.1?

Rgds

[Blootix]

Did you uploaded the new files from release 3.3.1?

Rgds
Yes I did. I even did it again just to make sure. Still no effect the comment boxes are blank.

[sv1cec]

Yes I did. I even did it again just to make sure. Still no effect the comment boxes are blank.
Darn, how stupid I am, I wrote $wcomment, while the proper parameter for the templates is $wmessage.

Sorry Blootix, please use $wmessage instead of $wcomment in those two templates.

[Blootix]

Darn, how stupid I am, I wrote $wcomment, while the proper parameter for the templates is $wmessage.

Sorry Blootix, please use $wmessage instead of $wcomment in those two templates.
Thanks John. Now everything works correctly!