Two issues here The default page post type is page, not pages Your meta_query is wrong, it should be an array of an array, not just an array Your arguments should be $args = array( ‘post_type’ => ‘page’, ‘order’ => ‘ASC’, ‘posts_per_page’ => 50, ‘meta_query’ => array( array( ‘key’ => ‘field_5505a81b83234’, // field key generated … Read more
Fields in database tables can not contain other types of data than text strings and numbers, and variations of them like dates and times. The field meta_value of wp_postmeta is a text field. So, when you store an array as meta_value you are really storing a string containing the serialized data that represents the original … Read more
No, it’s not possible by using pre_get_posts alone. But you don’t have to use separate fields for the date. WP_Query, although doesn’t provide a simple query arg that would sort the posts by month and day only, you can use the posts_orderby filter hook to modify the ORDER BY clause (i.e. ORDER BY <the part … Read more
Your code should work in theory. Your failure is not caused by the code in your question but rather due to external factors. Something else is causing this failure DEBUGGING THIS ISSUE Turn on debug and check for obvious errors and warnings. This should be a good indication on the soundness of all your code … Read more
Do NOT use query_posts() – it is bad, very bad to be exact. For more information read: When should you use WP_Query vs query_posts() vs get_posts()? When to use WP_query(), query_posts() and pre_get_posts Use WP_Query instead. Example with meta_key, meta_value and meta_compare parameters in use: $args = array( ‘meta_key’ => ‘clpr_excoupon’, ‘meta_value’ => ‘0’, ‘meta_compare’ … Read more
In the meta_query arguments, try changing your ‘type’ => ‘CHAR’, to ‘type’ => ‘DATETIME’, You can opt for any one of these, depending your needs: type (string) – Custom field type. Possible values are ‘NUMERIC’, ‘BINARY’, ‘CHAR’, ‘DATE’, ‘DATETIME’, ‘DECIMAL’, ‘SIGNED’, ‘TIME’, ‘UNSIGNED’. Default value is ‘CHAR’. But wait! There’s more! 😉 It seems that … Read more
The problem is with the arg ‘meta_key’ => ‘meta_value’ – meta_key isn’t needed if you have a meta_query arg (despite what the codex appears to say) and its value here doesn’t make sense anyway – so just remove it. However it does point out a behavioural change in 4.1 as before the meta_key was ORed … Read more
From the Codex: Multiple custom user fields handling $args = array( ‘meta_query’ => array( ‘relation’ => ‘OR’, 0 => array( ‘key’ => ‘country’, ‘value’ => ‘Israel’, ‘compare’ => ‘=’ ), 1 => array( ‘key’ => ‘age’, ‘value’ => array( 20, 30 ), ‘type’ => ‘numeric’, ‘compare’ => ‘BETWEEN’ ) ) ); Try adding the 0 … Read more
How can I create a WP_Query that returns posts where one meta_value <= another meta_value
Inserting boolean term meta values When we add non-existent term meta with e.g. add_term_meta( 123, ‘test’, true ); then we are actually running the following insert : $wpdb->insert( ‘wp_termmeta’, array( ‘term_id’ => 123, ‘meta_key’ => ‘test’, ‘meta_value’ => true ) ); within the general add_metadata() function. Now wpdb::insert() is actually a wrapper for wpdb::_insert_replace_helper() that … Read more