error on certain sources...
patchak - August 15, 2007 - 21:32
| Project: | Content Blocker |
| Version: | 5.x-1.x-dev |
| Component: | user.inc |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Description
Hey there Nedjo,
Ona certain leech source I have this error on all feed items, and it seems to break the feed..
Here is the error, please not content blocker seems related to the issue:
user warning: Unknown column 'n.nid' in 'on clause' query: SELECT DISTINCT(n.nid), n.title FROM node n, leech_news_feed f LEFT JOIN leech_news_item lni ON n.nid = lni.nid WHERE ((lni.fid NOT IN(SELECT id FROM contentblocker WHERE type = 'leech_news_feed' AND uid = 1) OR lni.fid IS NULL) AND (n.uid NOT IN(SELECT id FROM contentblocker WHERE type = 'user' AND uid = 1) OR n.uid IS NULL)) AND ( f.nid = n.nid) in /var/www/html/geekfr/includes/database.mysql.inc on line 172.
Do you see anything special here?
Thanks,
Patchak
#1
Hmm. I don't immediately spot a problem with the query. Node table is given an alias of n, and the field nid exists in that table, so I'm not sure why it's being deemed an unknown column. Any ideas?
#2
well the only thing that changed recentrly on the site is that I upgraded to leech version 1.8.. Maybe something changed in leech.module that affects content blocker??
thanks
#3
Do you have any ideas of the steps I should take to debut this issue?? The mention of content blocker in the error makes me think that it's maybe related to this module and the upgrade of leech... but then again, the actual *bug* is not in content blocker, but in leech.
When I edit a feed item, the 'parent source' field is now empty as if the link between the feed item and the feed source is not passed there. Is this related in any way to contentblocker in your opinion?
Thanks,
Patchak
#4
Well I can confirm that the update to leech v1.8 changed something that seems to have created this bug...
Also I can confirm that content blocker is related to this problem, cause de-activating it from the site makes the error go away with 1.8 and also with the most recent 1.9...
I would be willing to sponsor the update of the module to leech 1.9.. interested in having a look?
Thanks
Patchak
#5
patchak has sponsored this patch for his website GeekOMatik.
This patch simply swap the order of two SQL instructions.
(It was necessary because it caused MySQL crash on some installations. Weird behavior.)
The real problem was leech I think.
See the leech patch here :
http://drupal.org/node/171157
Author : Roberto Gerola
#6
#7
This looks good. patchak, can you please thoroughly test and ensure this doesn't break any existing functionality? If not, you can set this to RTBC. Thanks.