Title: Error in WP 3.5
Last modified: August 20, 2016

---

# Error in WP 3.5

 *  Resolved [ronbme](https://wordpress.org/support/users/ronbme/)
 * (@ronbme)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/error-in-wp-35/)
 * This is in WP 3.5. (Not MultiSite)
 * Gives the following error:
    Missing argument 2 for wpdb::prepare(), called in\
   wp-content\plugins\cpt-onomies\cpt_onomy.php on line 260 and defined in \wp-includes\
   wp-db.php on line 990
 * Looks like it is missing a second argument.
 * I’m working with another plugin author. Same thing. Everything is fine in WP 
   3.4.2 but getting errors in WP 3.5.
 * Let me know if you need more info.
 * Ron
 * [http://wordpress.org/extend/plugins/cpt-onomies/](http://wordpress.org/extend/plugins/cpt-onomies/)

Viewing 12 replies - 1 through 12 (of 12 total)

 *  Thread Starter [ronbme](https://wordpress.org/support/users/ronbme/)
 * (@ronbme)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/error-in-wp-35/#post-3233207)
 * Rachel, this should help:
 * Changeset 22429
    Timestamp: 11/07/12 19:30:59 (3 weeks ago) Author: nacin Message:
 *  Enforce a minimum of two arguments for wpdb::prepare(). The first argument is
   the query (or fragment thereof), which is required. Additional arguments are 
   values to substitute into placeholders.
 *  This will generate E_WARNINGs for insufficient arguments when prepare() is called
   with no additional arguments. This should discourage improper uses of prepare()
   under the guise of safely running a query.
 *  props xknown. fixes #22262.
 * It looks like they are forcing wpdb to have a second argument.
 * Ron
 *  [Rachel Cherry](https://wordpress.org/support/users/bamadesigner/)
 * (@bamadesigner)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/error-in-wp-35/#post-3233280)
 * Thanks Ron!! I’ll get it all fixed up for the next update.
 *  [Rachel Cherry](https://wordpress.org/support/users/bamadesigner/)
 * (@bamadesigner)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/error-in-wp-35/#post-3233317)
 * I’ve got this all fixed for the next update! Thanks for the heads up!
 *  Thread Starter [ronbme](https://wordpress.org/support/users/ronbme/)
 * (@ronbme)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/error-in-wp-35/#post-3233326)
 * Great! Thanks Rachel!
 * I’m looking forward to it.
 * Ron
 *  [Brayne](https://wordpress.org/support/users/brayne/)
 * (@brayne)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/error-in-wp-35/#post-3233333)
 * Wouldn’t it be easy to simply add some code to line 990 in wp-db.php?
 * `function prepare( $query, $args) {`
 * Becomes
 * `function prepare( $query, $args = "" ) {`
 *  [pserafini](https://wordpress.org/support/users/pserafini/)
 * (@pserafini)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/error-in-wp-35/#post-3233335)
 * Hi there.
    First things first, thanks for the nice plugin !
 * Now, WP 3.5 has gone public and I need a fix as the update to wp-db broke quite
   a bunch of functionalities of my current project.
 * Do you plan to release the update anytime soon ?
 * Cheers !
 * p.
 *  [Rachel Cherry](https://wordpress.org/support/users/bamadesigner/)
 * (@bamadesigner)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/error-in-wp-35/#post-3233336)
 * I hope to push out the update tomorrow!
 *  [pserafini](https://wordpress.org/support/users/pserafini/)
 * (@pserafini)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/error-in-wp-35/#post-3233337)
 * That would be perfect !
 * Thanks for the quick answer ! Keep up the good work !
 *  [John](https://wordpress.org/support/users/groupewibi/)
 * (@groupewibi)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/error-in-wp-35/#post-3233339)
 * Thank u Rachel !
 * I going to make a fix quick in waiting the update tomorow.
 * B Regards,
 *  [rossebow](https://wordpress.org/support/users/rossebow/)
 * (@rossebow)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/error-in-wp-35/#post-3233340)
 * I’m also getting the error on line 1348 of cpt_onomy.php.
 * You can just add “, NULL” to the end of the wpdb::prepare() statement.
 * Ross
 *  [Rachel Cherry](https://wordpress.org/support/users/bamadesigner/)
 * (@bamadesigner)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/error-in-wp-35/#post-3233341)
 * CPT-onomies 1.2 is out and should take care of this. Thanks!
 *  [pserafini](https://wordpress.org/support/users/pserafini/)
 * (@pserafini)
 * [13 years, 5 months ago](https://wordpress.org/support/topic/error-in-wp-35/#post-3233342)
 * thanks !

Viewing 12 replies - 1 through 12 (of 12 total)

The topic ‘Error in WP 3.5’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/cpt-onomies_f2f2f2.svg)
 * [CPT-onomies: Using Custom Post Types as Taxonomies](https://wordpress.org/plugins/cpt-onomies/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/cpt-onomies/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/cpt-onomies/)
 * [Active Topics](https://wordpress.org/support/plugin/cpt-onomies/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/cpt-onomies/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/cpt-onomies/reviews/)

 * 12 replies
 * 6 participants
 * Last reply from: [pserafini](https://wordpress.org/support/users/pserafini/)
 * Last activity: [13 years, 5 months ago](https://wordpress.org/support/topic/error-in-wp-35/#post-3233342)
 * Status: resolved