reject comments does not work: WSN Support

Version: 4.1.54
Status: upgrade issue

reject comments does not work

fresco
Forum Regular

Usergroup: Customer
Joined: Feb 19, 2003
Total Topics: 23
Total Posts: 106

Posted 07/19/08 - 09:23 AM:	#1
Warning: mysqli_fetch_row() expects parameter 1 to be mysqli_result, boolean given in /home/.../.../.../databases/mysqli.php on line 23 Warning: mysqli_fetch_row() expects parameter 1 to be mysqli_result, boolean given in /home/.../.../.../databases/mysqli.php on line 23 Comment does not get rejected/deleted - gives above error

Paul
Administrator

Usergroup: Administrator
Joined: Dec 21, 2001
Location: Northern California
Total Topics: 57
Total Posts: 6316

Posted 07/19/08 - 08:08 PM:	#2
Works for me. Post the debug info. http://scripts.webmastersite.net/wsnlinks/wsnmanu...
"Do things you love doing, because then it ain't work. Don't do something you don't really enjoy, because you're never going to work hard enough at it." - Bob Young, founder of Red Hat

fresco
Forum Regular

Usergroup: Customer
Joined: Feb 19, 2003
Total Topics: 23
Total Posts: 106

Posted 07/20/08 - 09:56 PM:	#3
it's weird but I can make it show queries.. It shows all queries accept when I go to validate page - it does not show queries...

fresco
Forum Regular

Usergroup: Customer
Joined: Feb 19, 2003
Total Topics: 23
Total Posts: 106

Posted 07/20/08 - 10:53 PM:	#4
when i tried to delete it through "edit comments" got this: Warning: mysqli_num_rows() expects parameter 1 to be mysqli_result, boolean given in /home/.../.../.../databases/mysqli.php on line 20 Non-numeric id value given in creating object. WSN Links 4.1.55

fresco
Forum Regular

Usergroup: Customer
Joined: Feb 19, 2003
Total Topics: 23
Total Posts: 106

Posted 07/20/08 - 11:01 PM:	#5
I found the problem - the field "id" for comments table was not set to "auto_increment" ... this is not a bug, please delete the post

Paul
Administrator

Usergroup: Administrator
Joined: Dec 21, 2001
Location: Northern California
Total Topics: 57
Total Posts: 6316

Posted 07/21/08 - 02:47 AM:	#6
Well, the issue is how it came to lose its auto_increment. I've seen that happen before on sites that originated in really old versions, I believe it's because the original field type which the old setup created isn't compatible with auto_increment in newer mysql versions (what was allowed in mysql 3 may not be allowed in mysql 5). I'll see if I can add a column sanity check on upgrade.
"Do things you love doing, because then it ain't work. Don't do something you don't really enjoy, because you're never going to work hard enough at it." - Bob Young, founder of Red Hat

You don't have permission to post.