![]() |
Getting SQL Error , pls help
Hi,
first of all, i have to say, that i have used the Warning Hack from ZeroTolerance 1.5. By mistake i runned first the install script for AWS 3.1.9 instead of the upgrade script. Afterwards i have run the upgrade Script, no special Messages. Have edited all the Files. I have set the setting in the Admincp : If i hit "View Warnings Log" in Admincp, i am getting follwoing SQL Error : Code:
Ungueltige SQL-Abfrage: 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 all other options are working there. Second Problem. : If i try to Warn somebody from Postbit Legacy, i am gettin following Error : Code:
Ungueltige SQL-Abfrage: select * from warnings where warned_post='86444' AND warned_status='A' gr33tz |
Hi,
Getting a similar error message on the upgrade from Zero Tolerance's hack, I am using vb 3.0.7 though. Code:
Database error in vBulletin 3.0.7: Code:
Database error in vBulletin 3.0.7: |
Add the missing column, by running the following queries:
ALTER TABLE `".TABLE_PREFIX."warnings ADD COLUMN removed_by int(15) ALTER TABLE `".TABLE_PREFIX."warnings ADD COLUMN removed_date int(15) ALTER TABLE `".TABLE_PREFIX."warnings ADD COLUMN warned_status char(1) ALTER TABLE `".TABLE_PREFIX."warnings ADD COLUMN caused_ban char(1) These should fix the missing fields. Let me know if you get any more errors. It's strange, because these fields exist in the upgrade_warn.php file, and of course, in the install_warn.php file, so they should have been created in either case. Rgds |
Hi sv1cec,
Those queries did not work for me, what I did instead was uninstall using the uninstaller.php and then done a reinstall afterwards, that seemed to work fine, and now I have the AWS up and working fine :D So maybe H@K@N should try the same if thequery does not work for him. thanks |
4 me it worked .... but not with the Strings which was mentioned.
Don't know exactly, but i think the apostroph infront the Table_Prefix is not correct, so i have done this Statement in phpmyadmin, without Prefix. Now its working .... gr33tz |
LoL,
yes, the queries wouldn't work, not because of the first single quote, but because of a missing second single quote: ALTER TABLE `".TABLE_PREFIX."warnings` ADD COLUMN removed_by int(15) ALTER TABLE `".TABLE_PREFIX."warnings` ADD COLUMN removed_date int(15) ALTER TABLE `".TABLE_PREFIX."warnings` ADD COLUMN warned_status char(1) ALTER TABLE `".TABLE_PREFIX."warnings` ADD COLUMN caused_ban char(1) Sorry folks, I keep saying to myself, not to answer questions early in the morning. Rgds |
Hi sv1cec,
Thanks for the heads up :), anyway I am really happy with this hack, thanks very much for sharing!! |
Quote:
|
All times are GMT. The time now is 04:56 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 | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|