DB Error

Clicking a users warning link and I get this error:

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


Any ideas?

I know its a missing columb, but what text do I need to put it back?

Laters

Just came accross another DB error:

When I edit the warning options and save them, I get this DB error:

Database error in vBulletin 3.0.6:

Invalid SQL: update warning_options set
hierarchical='Yes',
automatic='No',
automaticpm='No',
autocomments='No',
warner='1',
automatic_warner='',
collector='',
banned_limit='7',
points_before_banned='5',
warnings_before_banned='10',
banned_usergroup_id='14',
troll_usergroup_id='4',
protected_usergroups='6',
aprotected_usergroups='',
restore_groupid='0',
incr_ban_days='Yes',
max_no_bans='3',
bans_mature='0',
viewoption='Mgm',
multiple_per_post='Yes',
send_pm_warning='Yes',
send_em_warning='Yes',
email_on_ban='Yes',
historical='Yes',
allowoffpost='Yes',
warnings_per_page='20',
textbutoption='Text',
modoption='All'
where oid='1'
mysql error: Unknown column 'modoption' in 'field list'

HELP

[Delphiprogrammi]

Originally Posted by The Realist

Clicking a users warning link and I get this error:

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


Any ideas?

I know its a missing columb, but what text do I need to put it back?

Laters

yeah you're missing a table run this MySQL query

ALTER  TABLE `".TABLE_PREFIX."warnings`ADD COLUM warned_status char(1);

carefull with TABLE_PREFIX .... open install_warn.php there you can see the sql code ...

Originally Posted by The Realist

Clicking a users warning link and I get this error:

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


Any ideas?

I know its a missing columb, but what text do I need to put it back?

Laters

Just came accross another DB error:

When I edit the warning options and save them, I get this DB error:

Database error in vBulletin 3.0.6:

Invalid SQL: update warning_options set
hierarchical='Yes',
automatic='No',
automaticpm='No',
autocomments='No',
warner='1',
automatic_warner='',
collector='',
banned_limit='7',
points_before_banned='5',
warnings_before_banned='10',
banned_usergroup_id='14',
troll_usergroup_id='4',
protected_usergroups='6',
aprotected_usergroups='',
restore_groupid='0',
incr_ban_days='Yes',
max_no_bans='3',
bans_mature='0',
viewoption='Mgm',
multiple_per_post='Yes',
send_pm_warning='Yes',
send_em_warning='Yes',
email_on_ban='Yes',
historical='Yes',
allowoffpost='Yes',
warnings_per_page='20',
textbutoption='Text',
modoption='All'
where oid='1'
mysql error: Unknown column 'modoption' in 'field list'

HELP

ok settle down and please download the latest version the errors you are describing about missing database tables are telling you are trying to install an outdated version of this hack

[The Realist]

This is the latest version.

Ran your SQL code and received this error:

SQL-query:

ALTER TABLE `".TABLE_PREFIX."warnings` ADD COLUM warned_status char( 1 )

MySQL said: Documentation
#1103 - Incorrect table name '".TABLE_PREFIX."warnings'

[Delphiprogrammi]

yeah,

i already warned you about "TABLE_PREFIX" he that's a global vb varible for people that use database prefixes (for the tables) so if your table name is without prefix the query becomes

ALTER TABLE warnings  ADD COLUMN warned_status char( 1 )

ok you might have the latest version BUT if you want to upgrade and you are running an old verion you must perform ALL of the mentioned steps in UpgradeToLatestVersion.txt file the modoption querry is

ALTER TABLE `".TABLE_PREFIX."warning_options` ADD COLUMN modoption char(3)

again remove the "TABLE_PREFIX" if you don't need it

[The Realist]

When I click the view warning logs, I get this DB error:

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
warnings w
left join user wuser on(wuser.userid=w.warned_user)
left join user u on(u.userid=w.warned_by)
left join user ruser on(ruser.userid=w.removed_by)
left join warning_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

Not my day.

[Delphiprogrammi]

hi,

what are you doing you must install this hack the following way

• upload the hack files to your server (keeping the standard vb directory structure intact
• run install_warn.php(lataest version)
• do ALL of the .php files and templates edits

then and only then you can try to see if it works i think you are trying to see if it works when you are not completely done yet.The database errors you are getting can only be caused by incomplete or outdated installations

[The Realist]

I have installed it as you stated. The DB errors are still there:

When I click view log I get a DB error, but now when I click view warnings in a post or if I attempt to give a warming all I see is a white page and thats it?

[Delphiprogrammi]

hi,

well that's odd the "blank page" is a known problem first question i have in this problem

do you use more then one vbulletin style ? if yes then you can use this hack to copy the modified templates to all styles you use (requirerd) also do you use the files from this this thread ?

[The Realist]

I do have more than style but only use one.

also do you use the files from this this thread ?

No I used the original thread.

If the blank pages are a known problem, then whats the fix if there is one?

Thanks for your help by the way.

Regards.

[Delphiprogrammi]

hi,

usually blank pages turn up if you use custom styles but you aren't ... did you got any errors when you edited the templates ? daim this is odd i need some sleep now no more ideas when i wake up tomorrow morning i might have a new idea also there was a problem with an earlies release of aws i believe John updated the files in that "sticky" thread here in this forum