I tested your all attempts in a shortcode: function add_test_shortcode() { global $wpdb; global $post; $post_ID = $post->ID; $wpdb->show_errors = true; $result = $wpdb->get_var(‘SELECT meta_value FROM ‘.$wpdb->postmeta.’ WHERE meta_key=”my_test” AND post_id=’ . $post_ID); return $result; } add_shortcode( ‘test’, ‘add_test_shortcode’ ); It worked perfectly for me, so there might something from your own code: 1. Check … Read more
It’s not a normal practice to use raw SQL in WP, unless you absolutely have to. You should be using normal WP APIs for this and optimizing after you encounter a performance issue. Among other things APIs will transparently cache data (such as post meta) within page load and between page loads with Object Cache … Read more
I had to use two separate queries. The $wpdb->update syntax cant deal with calculating based on the existing value. But for the other two fields it works. So like this: $table = $wpdb->prefix . ‘woocommerce_downloadable_product_permissions’; $expiry_date = date(“Y-m-d”, strtotime(“+ 30 days”)); $expiry_time = $expiry_date . ‘ 00:00:00’; $wpdb->query(“UPDATE $table SET download_count = (download_count + 1) … Read more
So in this case, the problem is that your line right before the echo call is incomplete: $number_rows= $wpdb->get_var( “SELECT COUNT(*) FROM $wpdb->daviddgl_wp1.SaveContactForm7_7” ); $x=1; while ($x<$number_rows) { $results = $wpdb->get_results(“SELECT ticket, name,email FROM $wpdb->daviddgl_wp1.SaveContactForm7_7 WHERE id = $x”); print_r($results); $x++; } (You’re missing the closing bracket and semi-column) Note also that your echo will … Read more
Prepend the table prefix to iyzico_order_refunds instead of the $wpdb object: $payment_transaction_id = $wpdb->get_var( “SELECT payment_transaction_id FROM {$wpdb->prefix}iyzico_order_refunds} WHERE order_id=769 AND item_id=760” );
The main problem is how you’re specifying the custom table name (e.g., $wpdb->cf7dbplugin_submits). $wpdb only knows about the “built-in” tables when accessing a table name via $wpdb->xxx. To specify access a custom table name, use {$wpdb->prefix}custom_table_name. The other thing I notice is that, for security purposes, you should never use interpolated variables in an SQL … Read more
I have checked your code and I think there are the couple of things you have to consider: table prefix column name validate get_results function output Firstly, the original prefix is defined in wp-config.php. The WordPress $wpdb class provides a variable $prefix. Always use $wpdb obefore table name and it will automatcially insert the table … Read more
Line 3846 in wp-includes/functions.php is in a function named _deprecated_function(), which warns about the use of deprecated functions. I did a quick search of my copy of 4.9.4 core and didn’t find any instances of wpdb->escape() or get_current_site_name(), the two functions you’re actually being warned about. Most likely, the deprecated functions are in a plugin … Read more
Well, there are many things that are not exactly correct with your code: $posts = $wpdb->get_results( “SELECT ID, post_title, post_modified_gmt FROM $wpdb->posts LEFT JOIN $wpdb->term_relationships as t ON ID = t.object_id WHERE post_type=”post” AND post_status=”publish” AND t.term_taxonomy_id = 3 WHERE post_status=”publish” # <– !! second WHERE clause AND post_password = ” AND post_type=”post” # <– … Read more
Well, since I haven’t used a LIKE in a plugin in a while, it seems I missed this one. WP is now adding ‘placeholders’ whenever you prepare or esc a query. The short solution I found was to do this. It may not be the proper one, but it works. $sql = $wpdb->remove_placeholder_escape($wpdb->prepare(“SELECT ID FROM … Read more