vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   Advanced Warning System (AWS) (https://vborg.vbsupport.ru/forumdisplay.php?f=105)
-   -   The SQL Queries... for the Upgrade Instructions (https://vborg.vbsupport.ru/showthread.php?t=78380)

Blootix 03-19-2005 05:47 PM
The SQL Queries... for the Upgrade Instructions
 
When I executed that:
Code:
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:
Code:
DROP TABLE `".TABLE_PREFIX."warning_options`
there was:
Code:
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,
Quote:
you'll
it comes out to be
Quote:
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:
Code:
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
Code:
$message=$pm_message;
.

sv1cec 03-20-2005 05:05 AM
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 03-20-2005 05:08 AM
Quote:
Originally Posted by 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.
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 03-20-2005 06:03 AM
Quote:
Originally Posted by Blootix
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:

HTML Code:
Dear $user[username],

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

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

For this violation, you have been given : [b]$warn_type[warn_points][/b] point(s).
The point(s) will remain in your account for [b]$warn_type[warn_maturity] days[/b].
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:

=======================================
[i]$_POST[comment][/i]
=======================================

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

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

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

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 03-20-2005 07:57 AM
1 Attachment(s)
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 03-20-2005 10:20 AM
Quote:
Originally Posted by 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?
Did you uploaded the new files from release 3.3.1?

Rgds

Blootix 03-20-2005 03:19 PM
Quote:
Originally Posted by sv1cec
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 03-20-2005 03:42 PM
Quote:
Originally Posted by Blootix
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 03-20-2005 04:01 PM
Quote:
Originally Posted by sv1cec
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!


All times are GMT. The time now is 11:36 AM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01869 seconds
  • Memory Usage 1,745KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (5)bbcode_code_printable
  • (1)bbcode_html_printable
  • (8)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (9)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 
Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 
Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete