You can filter query. See wpdb::query() in wp-includes/wp-db.php. You get the complete SQL string as parameter. Then look for queries to the comments table: add_filter( ‘query’, function( $query ) { global $wpdb; if ( FALSE === stripos( $query, “FROM $wpdb->comments” ) return $query; // Now change the SQL }); But you have to catch all … Read more
Since version 3.9 (that will be released soon, actually in beta 2) WordPress will use mysqli to connect to database (3.9- versions use mysql) so you can actually use new wpdb instances and helper function to connect externa values from WordPress. What I suggest is to configure external database using constants in wp-config.php in this … Read more
What WP does for arrays (and objects) on some contexts (such as post fields) is using maybe_serialize()/maybe_unserialize() to turn such types (and just them) to and from serialized (string-typed) representation. While this simplifies workflow it comes with penalties, such as being unable to properly query through such data and common issues with migration (seriazlization-unaware tools … Read more
You can just call get_user_meta without specifying a key, and it will return all MetaValues for the user. $userdata = get_user_meta( $userID ); You may have to do a mapping for displaytitles of the Metavalue, as they are returned in an array, where the keys are the databasevalues of your metakeys. For example, you may … Read more
It depends on local factors and actual usage patterns. Bigger queries require more memory to store the data and potentially, depending on the plugins you use, to process it into the response, therefor you are more in a risk of running out of memory. With Bigger response (i.e. bigger page HTML) it takes more time … Read more
It may be because group doesn’t exist in the postmeta table. Your meta_key is probably called group and has a meta_value of bicyclegroup. This is assuming you haven’t modified the postmeta table. What you could try is: $sql = “SELECT * FROM $wpdb->postmeta WHERE meta_key = ‘group’ AND meta_value=”$group””; This will return: meta_id post_id meta_key … Read more
I would use a custom query like this: $amsterdamstore_args = array( ‘post_type’ => ‘store’, // This is your custom post type ‘tax_query’ => array( array( ‘taxonomy’ => ‘city’, // This is your custom taxonomy ‘terms’ => ‘Amsterdam’, // The term you search for ‘field’ => ‘name’, // Check against the term’s name (you might use … Read more
WordPress uses a prefix by default just in case the database is being used by more than WordPress. Since creating a new DB is pretty simple I would go that route. You would get the potential benefit of it being something separate that you can easily export, import or blow away if needed and also … Read more
If we look at the WP_REST_Controller::get_collection_params() method, we can see the minimum is 1 and the maximum is 100: ‘per_page’ => array( ‘description’ => __( ‘Maximum number of items to be returned in result set.’ ), ‘type’ => ‘integer’, ‘default’ => 10, ‘minimum’ => 1, ‘maximum’ => 100, ‘sanitize_callback’ => ‘absint’, ‘validate_callback’ => ‘rest_validate_request_arg’, ), … Read more
IF you want, you can disable revisions in first place (No need to run CRON then) To disable them go to wp-config.php and add this line: define(‘WP_POST_REVISIONS’, false ); Or to limit to 10 revisions define(‘WP_POST_REVISIONS’, 10); And to delete all current revisions you can run this SQL query: DELETE FROM wp_posts WHERE post_type = … Read more