Missing argument wpdb: in 3.5 Final

I made Ranno’s modification ( adding a ‘null’ argument) but I still have the error.
More precisely: when I display ALL items then I don’t get error message, but when I filter to eg. FEATURED items or want to display any FILTERED list then I’ve got the error!

Ranno Rocks !

Merci Ranno ! It works with PageLines Framework theme. It was NextGen that referred me to your post. Thanks again !

Ranno, you are the man! Thank you so much!!! Your fix worked perfect, I was going to lose it, but thanks to you my little site is up and running again. All the best!

Thanks Ranno~~for the temporary fix; worked and got rid of the code showing up on my frontpage! Now, hopefully they’ll update the plugin!

Namaste

Velma

I’m back to thank Ranno.
I tried your suggeston again and it worked!

I have Mindstream theme. I did turn off all the plugins–the error was still there. I have the current WordPress update.

One thing I got complacent about was updating too quickly. Never will I do that again. I used to wait a week to see if this type issue happened. Only when it was resolved did I update. I was too quick on the trigger this time. Live and learn–and be grateful for kind people like Ranno!

ranno’s fix is a temp like he said, but anyone who want can’t make the permanent fix (the one this error code is intended to trigger):

Just go to tags.php, on line 318, and replace this:

$term_ids = $wpdb->get_col( $wpdb->prepare(“SELECT term_id FROM $wpdb->terms WHERE slug IN ($sluglist) ORDER BY term_id ASC “));

with this:

$term_ids = $wpdb->get_col( $wpdb->prepare(“SELECT term_id FROM %s WHERE slug IN (%s) ORDER BY term_id ASC “,$wpdb->terms,$sluglist));

The idea behind it is to force the correct use of $wpdb->prepare. To prepare a query, you always need at least two arguments, and no variable should go in the first.

THANK YOU !!! YOU MAKE IT !!!!!!

Fantastic, worked thank you!

Thanks Ranno it worked. I really needed it to work, i want to let you know i am extremely grateful

I changed line 990 to this in wp-db.php:

/*
Set args = null in function below to avoid future problems with other plugins. I assume WordPress will do something similar in a future update, but this works for now.
*/
// OLD FUNCTION
// function prepare( $query, $args ) {
// NEW FUNCTION
function prepare( $query = null, $args = null ) {

@drmcatcher
Maybe it’s not so good idea to mess with wp-db.php file.

After all, it was NextGen the cause of the problem, not WordPress itself.

By doing that you are ignoring potencial plugin bugs that may allow SQL Injections on your site.
This means that your entire database may eventually be deleted by some less-than-honest-but-IT-aware user.

Maybe you should stick with correcting the bug in NextGen, instead of creating one in WordPress… ??

@drmcatcher – nunopicado is right!

There is a solution here posted by Ranno. It is a temporary solution, and the changes made will be over written when NextGen updates the plugin. There is no need to make changes to the core files of WordPress.

There is also a permanent solution (the correction Photocrati will probably make to NextGen) a few posts above, that I stated.

It’s just about using wpdb->prepare the way it’s supposed to, and all will be fine.

thank you ranno, totally fixed me up!