When accepting user data inputs, I think that data validation must be performed if possible, not only sanitization. For example, you could expect a number, a bool value, a text string (even when the input is a selectbox it can have a string value), etc. You can santize for that data types; then you can … Read more
Just add an underscore before the metabox ID so the part of your code where you add a metabox looks something like this: $id = ‘_drama-description’; $title=”Description”; $callback = ‘drama_description_metabox_markup’; $screen = $post_type; $context=”normal”; $priority = ‘high’; $callback_args=”null”; add_meta_box($id, $title, $callback, $screen, $context, $priority, $callback_args); You also need to replace every occurance of drama-description to … Read more
It is quite complicates grouped request, so to avoid problems, consider to use Cleanup Duplicate Meta plugin. The reason why duplicate entries are occured is usage of add_post_meta(). Just use update_post_meta() (even to create meta, it works) – and you will have always one meta field with certain name per post.
When multiple meta values are used for same meta key, WordPress store the values in different database rows. So every array, is stored in one row. Initial Data Let’s assume you have an array like this: $family = [ ‘father’ => [ ‘John’, ‘Doe’, 40 ], ‘mother’ => [ ‘Jane’, ‘White’, 39 ], ‘child_1’ => … Read more
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