You can achieve the OR relation using the tax_query argument like so: $query->set( ‘tax_query’, array( ‘relation’ => ‘OR’, array( ‘taxonomy’ => ‘category’, ‘terms’ => array( 2, 3 ), ), array( ‘taxonomy’ => ‘post_tag’, ‘terms’ => array( 10, 13 ), ), ) );
It looks like I’ve managed to work it out. I needed to: JOIN to wp_posts With the link keys: TABLE : wp_postmeta column : meta_key TABLE : wp_posts column : ID SELECT * FROM wp_terms wpt LEFT JOIN wp_termmeta wptm ON wptm.term_id = wpt.term_id AND wptm.meta_key = ‘thumbnail_id’ LEFT JOIN wp_postmeta wppm ON wppm.post_id = … Read more
what you are getting is a sql statement not a sql query result. actually die is a function so should be die(); when using print_r($query); die(); $rows = $wpdb->get_results($query); the second line will just not be used, so no results will be display from the query, this said, $query is a php variable that will … Read more
That’s not what esc_sql is for, or what it should be used for. Safely Escaping Variables In SQL Queries To make variables safe for an SQL query, use $wpdb->prepare, e.g. $table_name = “{$wpdb->prefix}myTable”; $myID = 12; $wpdb->query( $wpdb->prepare( “UPDATE `$table_name` SET `your_column_1` = 1 WHERE `$table_name`.`your_column_id` = %d”, $myID ) ); Notice that $myID is … Read more
It isn’t showing wp_posts.post_content LIKE ‘%test%’ because the wildcards (%) in the prepared statement are converted to placeholder escape strings (like the {a19f0a6c3d866f7270be0f3954cbb2600270400c15f488e112449a8a131701f0} in your post) when wpdb::prepare() calls wpdb::add_placeholder_escape() which “Adds a placeholder escape string, to escape anything that resembles a printf() placeholder“, i.e. a placeholder like %s. But those placeholder escape strings will … Read more
One possible solutions is use Queries in the joins instead of tables. so the query would look something like //read products with thumbnail and sku SELECT products.*, skus.sku, thumbs.thumbnail FROM `wp_posts` as products LEFT JOIN ( SELECT posts2.ID, pm1.meta_value as sku FROM `wp_posts` as posts2 LEFT JOIN `sf_postmeta` as pm1 ON posts2.ID = pm1.post_id WHERE … Read more
I managed to fix this myself with the following <?php if (isset($_GET[‘id’])) { $id = $_GET [‘id’]; } else { $id = “”; } //$url = “http://18.168.90.222/device-repair-service/device?id=$id”; require ‘sql_connect.php’; try { $connection = new PDO($dsn, $username, $password); $connection -> setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION); //echo “connection succesful”; } catch (PDOException $error){ echo $error -> getMessage(); } //prevent SQL … Read more
You were starting on the right track but you had several bits of WordPress hookage you still needed to add. An approach I like to use is to encapsulate a call to get_calendar() in a class so we can use the low-level ‘query’ hook but only use for it for the one call. So I … Read more
You’re probably better off doing this with wordpress functions and adding a button which would delete all posts (or even having a shortcode that, when loaded, would do it). The reason I recommend doing this instead of SQL directly is that wp_delete_post() will take all the associated meta with it, which saves you having to … Read more
There are some instances of serialized data in the database, notably in things like widget options, that become invalidated if you do a blind search-and-replace without accounting for different string lengths. You might try a tool like this one to do a search and replace that also handles serialized data: https://interconnectit.com/products/search-and-replace-for-wordpress-databases/