This will do. The slug is saved on the wp_posts while custom fields are on the wp_posts_meta. If you want to make it like that you can use an action hook on save_post that will get the value of the custom fields and saves it as the post slug. Here is the code add_action(‘save_post’, ‘set_slug’); … Read more
I figured I’ll leave the meta values saving on multiple fields in the db, because I’ve been doing allot of pre_get_post query filtering. Some of the features in there are for searching/filtering on post meta data and would it start making things very difficult if I was to start saving values into doubly serialized values. … Read more
Through a lot more research and some trial and error, I figured out the correct code to use that will restrict a post from being edited based on the user ID AND a custom meta field. $user = get_current_user_id(); $super_users = array(1); The first two pieces of code within the function are important for restricting … Read more
“You should not write to the DB on front end requests” is the eleventh commandment. Your performance will deteriorate due to the writes locking down the table much more than the impact the size of the table will have. You should probably write such data in files instead of DB, or at least use a … Read more
Note! This code was not tested! <?php function my_visitor_cookie($post_id) { if ( empty($post_id) ) { global $post; $post_id = $post->ID; } // get post meta $count = get_post_meta($post_id, ‘unique_post_visits’, true); // if there was no meta value if( empty($count) ) { $count = 0; } // check if cookie was already set (cookie name for … Read more
You’re almost there — you just need to add the comparison to your meta query: $args = array( ‘post_type’ => ‘product’, ‘meta_query’ => array( array( ‘key’ => ‘artist’, ‘value’ => $artistID, ‘compare’ => ‘=’ ) ) ); https://codex.wordpress.org/Class_Reference/WP_Meta_Query Remember to filter $artistID before accepting it in your query!
The ability to store abstract key-value pairs without modifying the database structure is the reason. Without that, WordPress loses much of its flexibility. I can’t speak for others, but the single largest reason why I develop atop WordPress is its flexible nature. To quote one of your links above, Usually the reasoning behind doing what … Read more
I have managed to fix it at my own. I have used following code to update post meta update_post_meta($post_id, ‘tb_data’, base64_encode(serialize($new_value_array))); …and following code to get post meta $tb_meta = get_post_meta($post->ID, ‘tb_data’, true); $tb_meta_unserialized = unserialize(base64_decode($tb_meta)); I hope this will help someone.
If you want to hide all the metaboxes for all users, you can do that through the get_user_option_metaboxhidden_{cpt}, default_hidden_meta_boxes or the hidden_meta_boxes filter, according to the /wp-admin/includes/screen.php file. Here’s an example for the post post type: /** * Hide all metaboxes in the global $wp_meta_boxes */ add_filter( ‘hidden_meta_boxes’, function( $hidden, $screen, $use_defaults ) { global … Read more
When you are saving the multidimensional array you can use this code: $product_img_path[$count][‘wpc_resize_thumb_img’] = $upload_dir[‘url’].”https://wordpress.stackexchange.com/”.$resize_img_name; $product_img_path[$count][‘wpc_resize_bid_img’] = $upload_dir[‘url’].”https://wordpress.stackexchange.com/”.$resize_big_img_name; update_post_meta($post->ID, ‘wpc_images’, $product_img_path); That way you can get multidimentional array like you want: Array ( [1] => Array ( [wpc_resize_thumb_img] => http://localhost/test/wp-content/uploads/2015/06/Wallpaper_55-212×159.jpg [wpc_resize_big_img] => http://localhost/test/wp-content/uploads/2015/06/Wallpaper_55-500×375.jpg ) [2] => Array ( [wpc_resize_thumb_img] => http://localhost/test/wp-content/uploads/2015/06/Wallpaper_51-212×141.jpg [wpc_resize_big_img] => http://localhost/test/wp-content/uploads/2015/06/Wallpaper_51-500×333.jpg ) … Read more