The two most obvious things you can do to reduce the load time of this query are the IN statement and the offset in your LIMIT statement. The larger the number of items you’re checking for in the IN statement, the less efficient the query. See: https://stackoverflow.com/questions/4514697/mysql-in-operator-performance-on-large-number-of-values The reason the offset is causing performance issues … Read more
To insert data you should use query() (documentation), get_var() method is for selecting data. If error is encountered, query() returns FALSE. query() This function returns an integer value indicating the number of rows affected/selected for SELECT, INSERT, DELETE, UPDATE, etc. For CREATE, ALTER, TRUNCATE and DROP SQL statements, (which affect whole tables instead of specific … Read more
Your code should look something like this: $this->table_name=”table_name”; $how_much = $this->wpdb->get_var(“SELECT COUNT(*) FROM $this->table_name”); We don’t need to use the prepare method, since this is not meant for table names, more here And also… as you what are trying to do is going not in a good direction… I don’t what to criticize you or … Read more
I strongly suspect the reason you want SQL that you haven’t mentioned/shared, is because you can’t use the WP functions to fetch the posts and do it manually in a single request due to the PHP time execution limit, or you don’t know how to. Sadly, doing it via SQL is no guarantee this will … Read more
You can do this using the WP APIs like this: $args = [ ‘post_type’ => ‘post’, ‘tax_query’ => [ ‘relation’ => ‘AND’, [ ‘taxonomy’ => ‘your_taxonomy_name’, ‘field’ => ‘slug’, ‘terms’ => array( ‘arizona’, ‘speech-language-pathology’ ), ] ], ]; $query = new WP_Query( $args ); Then you can use $query as you would any standard post … Read more
You should have not searched the field and replaced all the references to wp_ with anything. For example : the value of the entry with meta_key wp_page_for_privacy_policy will be change to wp_addtionnal_prefix page_for_privacy_policy. Hence there could be a lot of misfitted values in your table. A better way would have been to : export the … Read more
Option 1: backup – Many hosts offer backups. Sometimes you have to pay for them, but often even when you do, they’ve actually been backing everything up and paying just allows you to access them. Worth checking as this will be fastest. Option 2: post listing screen – If these posts all had only 1 … Read more
What you propose would break a lot of plugins and internals of WordPress. Post meta keys are not unique. This is supported at the API level too: // on save… add_post_meta( $post_id, ‘lead’, ‘Tom’ ); add_post_meta( $post_id, ‘member’, ‘Bob’ ); add_post_meta( $post_id, ‘member’, ‘Janet’ ); add_post_meta( $post_id, ‘member’, ‘Alice’ ); add_post_meta( $post_id, ‘member’, ‘David’ ); … Read more
Please try this code function search_by_sku( $search, &$query_vars ) { global $wpdb, $pagenow; if ( ‘edit.php’ != $pagenow || ! is_search() || ! isset( $query_vars ->query_vars[‘s’] ) || ‘product’ != $query_vars ->query_vars[‘post_type’] ) { return $search; } if(isset($query_vars->query[‘s’]) && !empty($query_vars->query[‘s’])){ $args = array( ‘posts_per_page’ => -1, ‘post_type’ => ‘product’, ‘meta_query’ => array( array( ‘key’ => … Read more
It would seem you have covered all your bases and your site is working as it should. An additional step I have found useful is to verify hard coded paths within your exported SQL file because problems might not appear for weeks after the move. I have moved a sites a few times and it … Read more