cant view polls after upgrading to 7.6 patch 3.1 [fixed]

Posted: Wed Nov 09, 2005 1:22 pm

hello.

I've just finished upgrading my site to phpnuke ver 7.6 with the 3.1 patch and I just finished installing Nuke Sentinel 2.2.0pl2. But since I've not been able to view any threads with polls. I get this error:

Code:

Could not obtain vote data for this topic





DEBUG MODE





SQL Error : 1030 Got error 28 from table handler





SELECT vd.vote_id, vd.vote_text, vd.vote_start, vd.vote_length, vr.vote_option_id, vr.vote_option_text, vr.vote_result FROM nuke_bbvote_desc vd, nuke_bbvote_results vr WHERE vd.topic_id = '536' AND vr.vote_id = vd.vote_id ORDER BY vr.vote_option_id ASC





Line : 701


File : viewtopic.ph

I know next to squat about SQL outside of basic editing/deleting. I checked the database using CHECK in Cpanel and even selected REPAIR but to no avail.

My site is: http://www.bani-league.com and here's a link that shows the error:

http://www.bani-league.com/modules.php?name=Forums&file=viewtopic&t=536

Not sure what else to do...

Posted: Wed Nov 09, 2005 1:54 pm

looking at the database and looking at the error I get, I see this:

Code:

WHERE vd.topic_id = '742' AND vr.vote_id = vd.vote_id

vd.topic_id matchs the db but vr.vote_id should "='42' "? (42 is the vote_id assinged in the db when I look at it through phpMyAdmin)
If this is correct, how do I go about fixing this?

Posted: Wed Nov 09, 2005 2:01 pm

I got it fixed.

I went to the VIEWTOPIC.PHP and looked for VR.VOTE_ID. The line vr.vote_id = vd.vote_id is correct, however, it was missing the apostrophies ( 'vd.vote_id').

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

That will not work. 'vd.vote_id' is NOT the same as vd.vote_id.

'vd.vote_id' will resolve to a literal string value equal to "vd.vote_id" as opposed to vd.vote_id which will resolve to the value of a column in the vd table named vote_id.

registered · Posted: Wed Nov 09, 2005 4:53 pm

Code:




Got error 28 from table handler

usually means that you have run out of temporary space

Talk to your host about it

Posted: Wed Nov 09, 2005 11:43 pm

hmm. temporary space? sql only takes up 18.5MB... I'll have to see.

Well. I can view the polls now but all polls show "nL" as options and dont post the results. This is on all polls; new and old. =/

here is a link to one: http://www.bani-league.com/modules.php?name=Forums&file=viewtopic&t=536

I have a test acount made up:

user: test
pass: password

I've browsed over the viewtopic.php min Modules/Forums but I'm too novice to notice something that doesn't appear out of place...

Posted: Thu Nov 10, 2005 12:27 am

MySQL needs temporary space in order to process the queries, especially when you have big JOIN tables or others. You'll really have to talk to your host about their configuration

Posted: Thu Nov 10, 2005 7:23 am

Your host should have temporary partition called /tmp. That's what Evaders is refering to. If your hosts doesn't have a good way of keeping that cleaned up, something akin to a garbage collection, then that folder/partition fills up and any application that needs a temporary work space can't work properly.

Posted: Thu Nov 10, 2005 9:04 am

So if they fix this, it would clear this problem up?

BTW, I forgot to mention that I looked at the database and my polls and votes are being recorded. Just not being displayed properly.

Posted: Thu Nov 10, 2005 11:06 am

We have been responding to your original post with this error message

Could not obtain vote data for this topic

DEBUG MODE

SQL Error : 1030 Got error 28 from table handler

SELECT vd.vote_id, vd.vote_text, vd.vote_start, vd.vote_length, vr.vote_option_id, vr.vote_option_text, vr.vote_result FROM nuke_bbvote_desc vd, nuke_bbvote_results vr WHERE vd.topic_id = '536' AND vr.vote_id = vd.vote_id ORDER BY vr.vote_option_id ASC

Line : 701
File : viewtopic.php

If you are still getting that error message then it's a HOST issue.

Posted: Thu Nov 10, 2005 9:34 pm

Raven wrote:

That will not work. 'vd.vote_id' is NOT the same as vd.vote_id.

'vd.vote_id' will resolve to a literal string value equal to "vd.vote_id" as opposed to vd.vote_id which will resolve to the value of a column in the vd table named vote_id.

I changed it back to the original format. Host fixed the issue.