This ended up being the correct formula in my case: $sql = “INSERT INTO foodWishes(foodWishName,foodWishPoints) VALUES (%s,%d) ON DUPLICATE KEY UPDATE foodWishPoints = foodWishPoints +1”; // var_dump($sql); // debug $sql = $wpdb->prepare($sql,$sanitized_foodWish,$foodWishPoint,); // var_dump($sql); // debug $wpdb->query($sql); if($sql){ //return the response echo $sql; }else{ echo “something went very very wrong”; } exit();
so if i have a function that gets terms from the database ( not the user ) do I need to use prepare first ( before get_results() ), or some sort of data sanitizing? Yes, but you should be using get_terms/WP_Term_Query/wp_get_object_terms/etc and the other term APIs instead as they’re safer and can be much faster. … Read more
Updating options via pure SQL is wrong. If you feel you have too many options to use the regular API you probably have too many options at all. A theme should not do the job a plugin can do. In fact, it should do as little as possible and let the user choose a plugin … Read more
You can do this one of two ways, as far as I can see: Use PHP to combine the current results to the one you want. Basically: $records = array(); foreach( $results as $result ) { $record_id = $result[‘item_id’]; if (empty($records[$record_id])) { $records[$record_id][‘item_id’] = $result[‘item_id’]; $records[$record_id][‘item_name’] = $result[‘item_name’]; $records[$record_id][‘sub_items’] = array(); } $records[$record_id][‘sub_items’][] = array( … Read more
Assuming that you mean that students is a table within your WP database, this should get you started. I’d recommend a read of the following materials, which are pretty useful – WordPress Codex for $wpdb. WordPress Codex for Theme Customization API. Here is the code to add the dorpdown box – /** Required to make … Read more
You can have problems only if database schema changed from older to new version. To know if the your is the case, you can compare the file wp-admin/includes/schema.php for both the versions, see that online here for 3.8.1 and here for 3.5.1. Note that a db index change should not beak the site, but it … Read more
Don’t use pure SQL if you don’t have to. WordPress provides a useful and relatively solid class for retrieving post data. Use it. $args = array( ‘post_type’ => array(‘post’,’page’), ‘post_status’ => ‘publish’, ‘posts_per_page’ => -1, ‘ignore_sticky_posts’ => true, ); $qry = new WP_Query($args); // Show post titles foreach ($qry->posts as $p) { echo $p->post_title; } … Read more
If you check out the source for the $wpdb->insert( $table, $data, $format) method you will find this comment: Data to insert (in column => value pairs). Both $data columns and $data values should be “raw” (neither should be SQL escaped). so you shouldn’t need to do the SQL escape yourself on the data. As far … Read more
$wpdb->get_results() returns an index array of row objects, but it looks like you’re expecting $exists to contain the actual value of the used column. you probably want $wpdb->get_var(): http://codex.wordpress.org/Class_Reference/wpdb#SELECT_a_Variable
The wp_rand function mixes up the randomization of random numbers with various means, and in between runs it stores the random seed so as to keep the shuffling going every run. The random_seed transient is where it stores that.