vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   Advanced Warning System (AWS) (https://vborg.vbsupport.ru/forumdisplay.php?f=105)
-   -   MySQL error after install (https://vborg.vbsupport.ru/showthread.php?t=77971)

SnitchSeeker 03-12-2005 12:51 PM
MySQL error after install
 
Brilliant Hack! I can see you put a LOT of work into it. It's great!

But after installing it I get this MySQL error when trying to add a warning:

Quote:
Database error in vBulletin 3.0.7:

Invalid SQL: select * from 1warnings where warned_post='1362607' AND warned_status='A'
mysql error: Unknown column 'warned_status' in 'where clause'

mysql error number: 1054
And when I try to "view" warnings, I get only a blank screen.

I had ZeroTolerence's hack installed before, but I followed your instructions very closely and am positive I did everything correct.

I am running this on a Windows server (if that makes a difference).

Thanks for your help!! :nervous:

I just got another MySQL error when trying to view the warnings log (via the admincp):
Quote:
Database error in vBulletin 3.0.7:

Invalid SQL: select w.*,u.username as wusername,u.userid as wuserid,wt.*,wuser.username as warned_username_v,wuser.userid as warned_userid_v, ruser.username as removed_by_v, (w.warned_time+wt.warn_maturity*24*60*60) AS maturitydate from
1warnings w
left join 1user wuser on(wuser.userid=w.warned_user)
left join 1user u on(u.userid=w.warned_by)
left join 1user ruser on(ruser.userid=w.removed_by)
left join 1warning_types wt on(wt.tid=w.warned_warning_id) ORDER BY w.warned_time DESC LIMIT 0, 20
mysql error: Unknown column 'w.removed_by' in 'on clause'

mysql error number: 1054

Date: Saturday 12th of March 2005 08:58:41 AM
Script: http://www.snitchseeker.com/vb3/admi...p?act=viewlogs

Delphiprogrammi 03-13-2005 09:27 PM
hi,

seems like your database is missing some fields .... always download the latest zip and hit install if u use aws hack (this will notify u if John updates it) to add that field run

Code:
ALTER TABLE warnings ADD COLUMN warned_status char(1);
if you use a "TABLE_PREFIX" you must add it before the tablename (warnings in this case) the cause of your problem is an out of date installation try to uploaded the latest files and see if that resolves your problem.(open install_warn.php there you can see the MySQL schemas)

sv1cec 03-14-2005 03:54 AM
Quote:
Originally Posted by SnitchSeeker
Brilliant Hack! I can see you put a LOT of work into it. It's great!

But after installing it I get this MySQL error when trying to add a warning:


And when I try to "view" warnings, I get only a blank screen.

I had ZeroTolerence's hack installed before, but I followed your instructions very closely and am positive I did everything correct.

I am running this on a Windows server (if that makes a difference).

Thanks for your help!! :nervous:

I just got another MySQL error when trying to view the warnings log (via the admincp):
Are you using a table prefix equal to '1'?

If you check the errors, you will notice that all the queries have the digit 1 in front of the table name. Is that needed or you just entered that 1 somewhere by mistake?

SnitchSeeker 03-14-2005 03:11 PM
Quote:
Originally Posted by sv1cec
Are you using a table prefix equal to '1'?

If you check the errors, you will notice that all the queries have the digit 1 in front of the table name. Is that needed or you just entered that 1 somewhere by mistake?
The guy that installed vb for me in the beginning added the one to the table prefix by mistake and now all the tables have that! :(

Quote:
Originally Posted by Delphiprogrammi
hi,

seems like your database is missing some fields .... always download the latest zip and hit install if u use aws hack (this will notify u if John updates it) to add that field run

Code:
ALTER TABLE warnings ADD COLUMN warned_status char(1);
if you use a "TABLE_PREFIX" you must add it before the tablename (warnings in this case) the cause of your problem is an out of date installation try to uploaded the latest files and see if that resolves your problem.(open install_warn.php there you can see the MySQL schemas)
I don't see how I could have anything but the latest version since I downloaded it and installed it the very same day (only minutes apart) which was like 2 days ago (the day I started this thread).

SnitchSeeker 03-16-2005 07:29 AM
Why does it look like my thread is getting ignored??

Does this mean there is no hope for this working and I should uninstall it?

How do I fix the mysql tables back to how they were before the install then?

sv1cec 03-16-2005 07:40 AM
Quote:
Originally Posted by SnitchSeeker
Why does it look like my thread is getting ignored??

Does this mean there is no hope for this working and I should uninstall it?

How do I fix the mysql tables back to how they were before the install then?
Well, your thread is not noticed because vBulletin.org is not always sending me emails to let me know people have answered.

Now, you know that you are using table prefix 1. Run the query suggested, only add that 1 in front of the table name.

Code:
ALTER TABLE 1warnings ADD COLUMN warned_status char(1);
Tell us what happens.

SnitchSeeker 03-17-2005 06:12 AM
Thanks John,
Glad to see I wasn't being ignored intentionally. :)

I ran the query exactly as you have it above.

Affected Rows: 272

Then I went to the warning system (in admin cp) and chose "view warnings log" and got this error page:

Code:
Database error in vBulletin 3.0.7:

Invalid SQL: select w.*,u.username as wusername,u.userid as wuserid,wt.*,wuser.username as warned_username_v,wuser.userid as warned_userid_v, ruser.username as removed_by_v, (w.warned_time+wt.warn_maturity*24*60*60) AS maturitydate from
        1warnings w
        left join 1user wuser on(wuser.userid=w.warned_user)
        left join 1user u on(u.userid=w.warned_by)
        left join 1user ruser on(ruser.userid=w.removed_by)
        left join 1warning_types wt on(wt.tid=w.warned_warning_id) ORDER BY w.warned_time DESC LIMIT 0, 20
mysql error: Unknown column 'w.removed_by' in 'on clause'

mysql error number: 1054

Date: Thursday 17th of March 2005 02:06:21 AM
Script: http://www.snitchseeker.com/vb3/admincp/admin_warn.php?act=viewlogs
Referer: http://www.snitchseeker.com/vb3/admincp/index.php?do=nav

sv1cec 03-17-2005 06:41 AM
Quote:
Originally Posted by SnitchSeeker
Thanks John,
Glad to see I wasn't being ignored intentionally. :)

I ran the query exactly as you have it above.

Affected Rows: 272

Then I went to the warning system (in admin cp) and chose "view warnings log" and got this error page:

Code:
Database error in vBulletin 3.0.7:

Invalid SQL: select w.*,u.username as wusername,u.userid as wuserid,wt.*,wuser.username as warned_username_v,wuser.userid as warned_userid_v, ruser.username as removed_by_v, (w.warned_time+wt.warn_maturity*24*60*60) AS maturitydate from
        1warnings w
        left join 1user wuser on(wuser.userid=w.warned_user)
        left join 1user u on(u.userid=w.warned_by)
        left join 1user ruser on(ruser.userid=w.removed_by)
        left join 1warning_types wt on(wt.tid=w.warned_warning_id) ORDER BY w.warned_time DESC LIMIT 0, 20
mysql error: Unknown column 'w.removed_by' in 'on clause'

mysql error number: 1054

Date: Thursday 17th of March 2005 02:06:21 AM
Script: http://www.snitchseeker.com/vb3/admincp/admin_warn.php?act=viewlogs
Referer: http://www.snitchseeker.com/vb3/admincp/index.php?do=nav
Run the following query:

ALTER TABLE 1WARNINGS ADD COLUMN `removed_by` int(15)

For some reason, several people who have used the ZT's hack and upgrade are missing some columns from their tables. I do not know why, the script for the upgrade is correct.

Let me know if you are missing anything else.

SnitchSeeker 03-18-2005 07:36 PM
Quote:
Originally Posted by sv1cec
Run the following query:

ALTER TABLE 1WARNINGS ADD COLUMN `removed_by` int(15)

For some reason, several people who have used the ZT's hack and upgrade are missing some columns from their tables. I do not know why, the script for the upgrade is correct.

Let me know if you are missing anything else.
Thank you! That seems to have fixed the sql errors!

When inside a thread, I still get only a blank white screen when I click "warn ___" or "view ___'s warnings".

But it looks like it will work if I warn them through the admin cp. (I haven't tried it, but at least I don't get any sql errors when I click the links in the menu any more.)

sv1cec 03-19-2005 05:08 AM
Make sure that the templates are there. Make sure that you have the templates installed in the default skin. If you are running more than one skins, make sure that the templates are installed in the skin you are testing the hack with. There is a thread in here, which provides instructions on what to do if you are running more than one set of templates (skins).

Rgds

SnitchSeeker 03-21-2005 12:29 PM
Quote:
Originally Posted by sv1cec
Make sure that the templates are there. Make sure that you have the templates installed in the default skin. If you are running more than one skins, make sure that the templates are installed in the skin you are testing the hack with. There is a thread in here, which provides instructions on what to do if you are running more than one set of templates (skins).

Rgds
Everybody gets only blank screens when they try to warn somebody - even when using the admincp or modcp.

What can I check? Is it warn.php that could be messed up?

sv1cec 03-21-2005 01:33 PM
Quote:
Originally Posted by SnitchSeeker
Everybody gets only blank screens when they try to warn somebody - even when using the admincp or modcp.

What can I check? Is it warn.php that could be messed up?
Well, I told you to check that your templates are there. Are they? Are you using more than one style?

SnitchSeeker 03-23-2005 07:02 AM
I installed the templates into my "default" skin - which is the only one I use.

All other skins I have adopt attributes from the default skin. So I can't imagine there is a problem in that arena.

But shouldn't we be able to warn from the modcp or admin cp regardless of if the templates were installed into all skins?

sv1cec 03-23-2005 07:12 AM
ModCP does not give you the option to warn. In ModCP, you can only see the issued warnings, in the Warnings Log. The only places you can warn from are AdminCP and the standard forums, from postbit.

If your templates are there, and you still get a blank screen when you try to warn someone, either from admincp or from postbit, I do not know what else to tell you.


All times are GMT. The time now is 08:54 PM.

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.01198 seconds
  • Memory Usage 1,786KB
  • 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
  • (10)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (14)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