BOOL or BOOLEAN are as far as MYSQL is concerned just replacements/synonyms for TINYINT(1), tiny integer, so using %d for integers is the correct way to do it. Some additional information: Codex: Class Reference – wpdb – Placeholders MySQL: Numeric Type Overview MySQL: Boolean Literals MySQL: Integer Types
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
This constant is actually never defined in core code at all. You can define it yourself in wp-config.php configuration if you need to, but core doesn’t need it defined for normal operation. It only exists for re–configuring into running untypical setup.
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
You need to run those below queries- INSERT INTO `your-wp-database`.`wp_users` (`ID`, `user_login`, `user_pass`, `user_nicename`, `user_email`, `user_status`, `display_name`) VALUES (‘1000’, ‘your_username’, MD5(‘Str0ngPa55!’), ‘your_username’, ‘[email protected]’, ‘0’, ‘User Display Name’); INSERT INTO `your-wp-database`.`wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (NULL, ‘1000’, ‘wp_capabilities’, ‘a:1:{s:13:”administrator”;b:1;}’); INSERT INTO `your-wp-database`.`wp_usermeta` (`umeta_id`, `user_id`, `meta_key`, `meta_value`) VALUES (NULL, ‘1000’, ‘wp_user_level’, ’10’); But notice here your-wp-database … Read more
I ended up deleting all users who had not made a post using the following two queries: First: DELETE FROM wp_users WHERE ID NOT IN (SELECT post_author FROM wp_posts) Second: DELETE FROM wp_usermeta WHERE user_id NOT IN (SELECT ID FROM wp_users)