Unknown column 'n.type' in 'where clause' query

Hi,

I checked the code: It's all correct.
I _REALLY_ think it's another module messing things up.
Please:

1) Give us a list of external modules you are using
2) Take those modules off one by one, and check CAREFULLY if the issue is not there. Try to locate which module is causing this
3) Let me know which module it is.

I am 98.87% sure it's another module messing up the query.

ALSO, please provide the exact step to reproduce this, "On my taxonomy pages" is not precise enough. You need to provide a list of URLs/operation your mum should be able to follow.

Bye!

Merc.

Hi,

How can another module cause this? Well, it's a bit of a long story...
Drigg does a "last minute rewrite" for every database query that is run. This is to guarantee that "killed" nodes are not fetched. I do this using a hook:

function drigg_db_rewrite_sql($query, $primary_table, $primary_field, $args){

Now, I am VERY specific in my hook function: it only works if the query passed works on a node:

// This will only filter node lists
if($primary_table=='n' && $primary_field == 'nid'){

When you run ANY query, modules surround the query with db_rewrite() which will in turn call the hook. That "n" means that the query is on a node, and that primary field is to check that the query's primary ID is "nid". However, db_rewrite() is a bit of a pain in that "n" and "nid" are the defaults. So, one of your extra modules is calling db_rewrite() around a query, AND it's leaving the defaults... AND it's doing so while running a query NOT on the node table.

Hence the mistake.

Now, if by this: "All modules to go step by step is not an option" you meant that you are not going to do what I asked, that is disable the modules one by one until the error goes, I am afraid I will have to mark this as a "won't fix" as that's the only way for me to investigate it. I don't mean this in a nasty way: it's just that I won't have a choice. I am already probably hunting a problem with *another* module. There is only so much I can do.

Bye,

Merc.

Hi,

There is nobody else who can help you, because it's definitely a problem specific with a specific module you are using right now.

You are the only person able to actually find it... the most important question is: which module is making the query?

Bye,

Merc.

Hi,

Sorry, the way to search depends on your OS and it's a little bit tricky. As I said, the best way is to disable one module at a time (see my detailed checklist/explanation above).

Bye,

Merc.

I had this error too I guess>

* user warning: Table 'dbtest.node' doesn't exist query: SELECT * FROM d5drigg_node dn LEFT JOIN node n on dn.dnid=n.nid WHERE dn.url='' in /home/www/test/www/m/includes/database.mysql.inc on line 172.

I made fresh install and problem disapeared sofar. The only difference is that I didnt put table prefix on fresh install, but I doubt thats the case...

Hi,

Ah!
Another bug!

Please change drigg/drigg/helpers.inc, line 653, from:

$sql = "SELECT * FROM {drigg_node} dn LEFT JOIN node n on dn.dnid=n.nid WHERE dn.url='%s' $nid_query";

Into:

$sql = "SELECT * FROM {drigg_node} dn LEFT JOIN {node} n on dn.dnid=n.nid WHERE dn.url='%s' $nid_query";

I can't believe I left it like that... sorry!

Summit: does this fix your bug too?

Bye,

Merc.

Hi,

Original poster: does #10 fix your problem too?
If not, please provide an update.

I will close this bug in 3 days unless more info is provided.

Merc.

Hi,

Summit: AH! So you are!
Ok, bug is squashed :-D

Merc.