SQL Errors on tagged nodes
| Project: | Tagnode |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
I'm using tagnode to link an "Event" node and a "Venue" node. I've set up the vocabulary with no problem and was able to make "Venue" a tagnode in content settings. My problem is, I keep getting SQL errors at the top of the page whenever I view both "Event" and "Venue" nodes.
warning: sprintf(): Too few arguments in /var/www/htdocs/drupal-4.6.5/includes/database.inc on line 154.
user error: Query was empty
query: in /var/www/htdocs/drupal-4.6.5/includes/database.mysql.inc on line 66.
Sometimes the previous errors appear twice on the same page. I created and viewed an untagged node and did not receive the errors, leading me to believe it's a tagnode-specific problem.
I thought perhaps it was related to this problem, so I tried downloading the CVS version (Dec 29 10:56:47 2005 UTC) of tagnode.module; but it does not work. It won't display the tagnode options under administer->content->configure->content types making it impossible to create a tagged node.
My site is Drupal 4.6 on Slackware, kernel 2.4.31, Apache 1.3.33, PHP 4.4.0, MySQL 4.1.16. If you need any more information, just ask. Thanks for your help.
#1
hershmire,
many thanks for this bug report! my debugging has been confounded, because i have been unable to reporduce. however i was able to implement some fixes i had put into the cvs version, which might explain your bug. i am hopeful the current 4.6 version would fix your bug. if you do still get the error, i'd greatly appreciate your letting me know some more details, e.g. what are all the settings you have for the vocabulary you are using for tagnode? how many nodes of each type (tagnode & taggee) have you defined? which modules do you have enabled. are there any other things idiosyncratic to your setup?
btw, the cvs version of tagnode is now for drupal 4.7. i have not branched/published it for 4.7 yet since i am unsure how stable. so far so good for me, and no bug reports in a while. not sure how much usage it's getting. if you try it i'd appreciate some feedback.
again, many thanks,
dado
#2
I found out some more info that may help your testing. I thought perhaps my issue was just from some misconfiguration, so I started with a new installation of Drupal and found something interesting:
The messages only occur when there are two vocabularies associated with a tagee node, one a tagnode vocabulary the other not. In my case, "event" has a "venue" (tagnode vocabulary) and an "event type" (non-tagnode vocabulary). I set-up the tagnode vocab first and it ran fine. The instant I added the second non-tagnode vocabulary to the node, the messages appeared.
My setup includes the location module and event module. Location is linked to the "venue" node, but the database errors still remain if I remove the location module. Every else is a vanilla install.
I'm guess tagnode is considering the other non-tagnode vocab as one of its own? Does that make sense?
#3
Accidently changed the title of this report. Still getting the hang of this issue reporting system...
#4
Great work hershmire! I was finally able to reproduce. I implemented a fix that works in my environment and committed to Drupal 4.6 version of tagnode, just now.
Please comment as to whether this works. Thanks,
dado
#5
-Tested and works in 4.6. Didn't try 4.7 since I don't have an install up and running. Guess my years working QA were worth it.
Thanks, dado, for offering a great module and for the quick turn-around time for fixes.
#6
I implemented similar fix for 4.7 version (now in CVS HEAD)
Thanks again
#7