If you’ve got 60,000 records, try cleaning post/page revisions; these really accumulate and cause excessively long queries. I’ve seen database sizes drop 90% with huge increases in performance. Run the query below in phpmyadmin or from the command line and then optimize: DELETE a,b,c FROM wp_posts a LEFT JOIN wp_term_relationships b ON (a.ID = b.object_id) … Read more
I don’t think you can do this. Maybe you could use a whole new database, but it seems unlikely you could add a new table for managing a custom post type. For one thing, a custom post type is stored in the wp_posts table, but some of the data for it gets stored in the … Read more
Does unregistering them the also disable the database queries? Goes in functions.php: //Unregister all Default Widgets function unregister_default_wp_widgets() { unregister_widget(‘WP_Widget_Pages’); unregister_widget(‘WP_Widget_Calendar’); unregister_widget(‘WP_Widget_Archives’); unregister_widget(‘WP_Widget_Links’); unregister_widget(‘WP_Widget_Meta’); unregister_widget(‘WP_Widget_Search’); unregister_widget(‘WP_Widget_Text’); unregister_widget(‘WP_Widget_Categories’); unregister_widget(‘WP_Widget_Recent_Posts’); unregister_widget(‘WP_Widget_Recent_Comments’); unregister_widget(‘WP_Widget_RSS’); unregister_widget(‘WP_Widget_Tag_Cloud’); } add_action(‘widgets_init’, ‘unregister_default_wp_widgets’, 1);
It’s set in schema.php, the WordPress Administration Scheme API. You can also find it in the Codex. As you can see from a search through core, there’s (as far as my search went) exactly no use case for it, aside from defining it as 0 when adding that option to the DB. If you want … Read more
$wpdb is outside the scope of your plugin file, you need global $wpdb; before using $wpdb->prefix
Tax Query Limits A Taxonomy Query in WordPress supports the following three arguments for the operator parameter: IN, NOT IN and AND. So it basically can’t do what you’re trying to do. Not even with advanced (tax_query) Queries. Meta Query and possibilities You’ll want to move your concept a bit and work with post meta … Read more
If you have databases reachable from the outside ie: mysql1.example.com you can work on a local development environment connected to that the whole time. I just found a nice thing to put in wp-config.php to be able to change the host depending on your environment $host = $_SERVER[‘HTTP_HOST’]; define( ‘WP_HOME’, ‘http://’ . $host ); define( … Read more
Problem is that meta values are not unique key/value data. E.g. with the key ‘OneKey’ you can have a lot of values for the same post. So, in a flat table, for the column ‘OneKey’ you should have multiple rows where the post id is the same and seems to me is not what you … Read more
You most probably only added one of the following in your wp-config.php file thinking they were the same, as m73mitchell and I had done: define(‘WP_ALLOW_MULTISITE’, true); define(‘MULTISITE’, true); I couldn’t find any documentation why they have this counterintuitive setup, but just add the one you missed and it should work.
What you did wrong here was to prepare those items in the first place. You only run “data” variables through prepare(). You don’t run table names, or sort directions, or limits through it. These are part of the SQL command itself, they are not data that refers to information which is stored in a column … Read more