I’ve spent hours of research and found the solution a few minutes after writing this question: $args = array( ‘post_type’ => ‘attachment’, ‘post_status’ => ‘inherit’, <<– IMPORTANT ‘meta_query’ => array( array( ‘key’ => ‘medientyp’, ‘value’ => ‘Video’ ) ) ); $query = new WP_Query($args);
Introducing STR_TO_DATE MySQL has a STR_TO_DATE function that you could leverage for the scope. To use it you need to filter the WHERE clause of a WP_Query, probably using posts_where filter. That function allows to format a column value as a date by using a specific format. By default, WordPress uses the CAST MySQL function … Read more
It depends on what exact action you are using, and what the purpose of that action is. For the update actions, for example, there should always be hooks that are triggered before doing the change (so that you may change or prevent it), and hooks that are triggered after the change has been completed (so … Read more
If you are working with serialized data as your meta_value, that sucks, as Pieter suggested, it’s best not to. However if there is no way around the serialization problem then I wonder if a meta_query using a compare value of LIKE might help… Example: //psuedo serialized data… (e.g. value of meta_key = fruits_user_like) //a:4:{i:0;s:5:”apple”;i:1;s:6:”orange”;i:2;s:6:”banana”;i:3;s:31:”serialized_data_sucks_sometimes”;} $users … Read more
What is the SQL query you are using? What are more details of the export and end format you need? The obvious things are 1) http://wordpress.org/extend/plugins/navayan-csv-export/ “Navayan CSV Export is a wordpress plugin to export all your table data in CSV (Comma Separate Value) format.” and 2), exporting with phpmyadmin – the database utility – … Read more
update_post_meta() calls update_metadata which begins with this line: if ( !$meta_type || !$meta_key ) return false; I wrote a simple test (with a lot of cut & paste) to see how string values of 0 are evaluated (instead of looking it up in the PHP manual): <?php $meta_key = (string) 0; if ( ! $meta_key … Read more
I think that you can improve performance saving view information in one single option instead in post meta applying the filter date on saving instead of on retrieving create the markup and save in a transient instead of saving the query (fragment caching) Rough implementation in a class class PopularPosts { const OPT = ‘myplugin_popular_posts’; … Read more
I do need to add both post_meta: add_post_meta( $insert_q_key_id, ‘q_key_type’, (int)$q_key_type ); // Q Key Type And for ACF: update_field( “field_52c737a413e07″, (int)$q_key_type, $insert_q_key_id ); // Q Key Type And the rest of the answer “should” be covered by wp_set_object_terms: wp_set_object_terms( $insert_q_key_id, (int)$q_key_type, ‘q_key_type’, true ); However, this function is not fully available at the point … Read more
You are facing an XY Problem. The only reason to save meta values each as a single row, would be if you need them to be searchable. If you need specific sanitization rules, use either filter_var_array() or sanitize the values, then build the array and finally save the value. Gist with a comprehensive filter_var_array() example … Read more
If you don’t feel any performance degradation then there is no problem. If it took you two years to get to this state then you probably safe for another two years, which is almost forever in the time scale of the internet (unless you are CNN or similar). This doesn’t mean that you should not … Read more