Unknown column 'q.vid' in 'where clause' query: SELECT q.author AS quotes_author, q.promote AS quotes_promote FROM quotes q WHERE q.nid = 14567 AND q.vid = 14568 in /home/knowpros/public_html/includes/database.mysql.inc on line 120.
As well as 'n/a' being displayed in quotes block, which this patch doesn't work either (thus, that is not fixed - at least for me).
Huh?
Checked the database - quotes is alive and well. So something appears to be wrong with the queries.
The nodes are legitimate; I repaired the Quotes table anyway... as well as the node table... but still.... why isn't it acknowledging quotes.vid as q.vid? Grr. Must be something simple if nobody else has seen this before.
Comments
Comment #1
Taran commentedBTW, this is Drupal 4.7.
Staring at the code....
Comment #2
jhriggs commentedDid you maybe have the old (non-4.7) cvs version installed before I release the 4.7 version? Go to update.php and see if it is showing any available updates for the quotes module. If so, perform them.
Comment #3
Taran commentedSure did... nailed. Thanks, this is fixed. Perhaps the readme should have this... but this is a pretty good document of the problem here... dunno.
I didn't think that update.php was related. Geez, how things change. :-) Thanks! I think you saved a few hairs.
Comment #4
jhriggs commentedWell, if you had upgraded to Drupal 4.7 with the 4.7 quotes module installed, it would have performed these updates along with the Drupal upgrade. It only didn't in your case because you must have had an old version installed when upgrading.
Comment #5
Taran commentedErr. No. I had the CVS version of Quotes installed when I was upgrading. I can't nail it down now, but I know that the quotes CVS did work to some degree with Drupal.
Sidenote: The whole 'module release' and 'core release' is in severe need of a reboot... not blaming anyone, but saying it could have been done much better. Sort of like not knowing when a module has changed, too... these are things that the Drupal community should probably look at. That's really been the main problem I've had with the upgrade to 4.7. Seemed like module developers were left in the cold a bit.
Comment #6
binford2k commentedBTW, the install file didn't automatically detect the database update. I manually forced the update to version 2 and it fixed the problem.
Comment #7
Taran commentedI didn't have that problem with the update. Maybe your quotes module was older?
Comment #8
(not verified) commented