WordPress.org

Ready to get started?Download WordPress

Forums

NextGEN Gallery
[resolved] Error in WP 3.5: Missing argument 2 for wpdb: (11 posts)

  1. Christine
    Member
    Posted 1 year ago #

    Warning: Missing argument 2 for wpdb::prepare(), called in /home/desert/public_html/wp-content/plugins/nextgen-gallery/lib/tags.php on line 318 and defined in /home/desert/public_html/wp-includes/wp-db.php on line 990

    Seems to have to do with my upgrade to WP 3.5.

    http://wordpress.org/extend/plugins/nextgen-gallery/

  2. shammah
    Member
    Posted 1 year ago #

    I just got the same message when I updated to 3.5:

    Warning: Missing argument 2 for wpdb::prepare(), called in /home/sham8551/public_html/wp-content/plugins/nextgen-gallery/lib/tags.php on line 318 and defined in /home/sham8551/public_html/wp-includes/wp-db.php on line 990

    and have no idea what to do! I am hosted on my own website using WP.

    Velma

  3. esmi
    Forum Moderator
    Posted 1 year ago #

    Don't panic. The front end of your site and the plugin should continue to work correctly but you will have to wait for this plugin to be updated before that warning in the back end disappears.

  4. Christine
    Member
    Posted 1 year ago #

    I did some reading on it and it looks like NOT a big deal and an update to the plugin will fix it. Just wait for that.

    OT: Maybe one of these days WP will have the option to REVERT after an upgrade if you encounter problems because I sure don't have time to back up every site. I don't understand how these errors happen after numerous betas and release candidates and this is NOT the only plugin affected.

  5. Christine
    Member
    Posted 1 year ago #

    Just saw esmi's post. The error seems to show on every post here:
    http://highdesertpermaculture.org/

  6. shammah
    Member
    Posted 1 year ago #

    This error message is clearly visible to the Public...and gives them too much info about my site and where things are found....i.e. the url to get in to the site? I don't like it being up and out there.

    http://shammahspace.ca/the-power-of-words/

  7. esmi
    Forum Moderator
    Posted 1 year ago #

    I don't understand how these errors happen after numerous betas and release candidates and this is NOT the only plugin affected.

    Unfortunately not all plugin developers take the time to test their plugins with the next beta release of WordPress - even though they had about 6 months of beta testing time with this core update.

    Even when plugins are tested, it's possible that an obscure bug can slip through.

    If you are seeing the error message on the front end of the site, then you should ask your hosts to suppress PHP warning - as most good hosts already do for security reasons.

  8. Christine
    Member
    Posted 1 year ago #

    Once again it's MY FAULT! I shoulda known. Just this morning my VPS host SolaDrive told me that my VPS had high loads at around 5 am due to the wordpress index.php and that I need to have the developers make some changes (my combined WP sites had a total of 70 page views by 9 am).

    I'm getting awfully sick of the fingerpointing!

    I suppose I'll just disable NextGen Gallery and use something else. I regret the donation I had made.

  9. photocrati
    Member
    Plugin Author

    Posted 1 year ago #

    Hey everyone,

    Please refer to this forum thread already created that addresses this bug, and provides a temp. fix until we release an upgrade: http://wordpress.org/support/topic/missing-argument-wpdb-in-35-final?replies=26#post-3560464

  10. tanirae
    Member
    Posted 1 year ago #

    My fabulous webhost, ixwebhosting.com, who allows you to call them just turned off the message so it no longer shows on my pages. when the upgrade comes in it will fix it without my having to do anything. So maybe your host can turn it off or tell you how.

  11. Christine
    Member
    Posted 1 year ago #

    My awful host SolaDrive just got most of my sites working yesterday after a life altering move and two weeks in SolaDrive HELL. It'll take me at least several weeks to recover (emotionally and financially) and quickly moving to some other host isn't an option.

    So, disabling NextGen did NOT work. Since there is no "delete" button for NextGen, I had to ftp and delete the plugin. That did the trick.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic