Yes there is Option API to store site global data. You can store some global values using add_option() then can retrive values as get_option() Example: add_option( ‘option_name’, ‘option_value’, ‘deprecated’, ‘yes’ ); //OR update_option(‘option_name’, ‘option_value’, ‘yes’); //Get the value $your_data = get_option(‘option_name’, ‘option_default_value’); echo $your_data;
I can already tell that you’re using ACF – if you don’t want to change the return settings for the field, you can bypass ACF and just pull the image ID directly from post meta: $image_url = get_field( ‘my_field_name’ ); $image_id = get_post_meta( $post->ID, ‘my_field_name’, true ); $image_meta = wp_get_attachment_metadata( $image_id );
Answer by @Gareth Gillman definitely works but its an expensive query if we have hundreds of posts. The function below is less expensive and using the wp native function get_post_custom_keys() if ( ! function_exists( ‘us_get_meta_keys_for_post_type’ ) ) : function us_get_meta_keys_for_post_type( $post_type, $sample_size = 5 ) { $meta_keys = array(); $posts = get_posts( array( ‘post_type’ => … Read more
You’re going to definitely want to do this with a plugin. Modifying WordPress Core files is an extremely bad idea as others have pointed out because every update will wipe them out and future versions may change the location/function of what you’re editing. You can get away by adding it to the theme’s functions.php file … Read more
Post’s metadata can not and should not be used for validation. They can be easily manipulated. Post metadata simply stores “editable” strings or arrays, nothing more than that. The code you have copied is trying to fetch a metadata and check if its value is mp3. You can change a value of exe to mp3, … Read more
There seems to be a bug in WordPress building the query. I had this exact same issue today, using ACF Pro. I passed an array to orderby, and it worked. This is my code: $args = [ ‘post_type’ => ‘event’, ‘meta_query’ => array( ‘key’ => ‘event_date’, ‘value’ => date(‘Ymd’), ‘type’ => ‘DATE’, ‘compare’ => ‘>=’ … Read more
You should ad the custom field to product API response, try this (untested) add_filter( ‘woocommerce_rest_prepare_product’, ‘custom_products_api_data’, 90, 2 ); function custom_products_api_data( $response, $post ) { // retrieve a custom field and add it to API response $response->data[‘purchasing_cost’] = get_post_meta( $post->ID, ‘purchasing_cost’, true ); return $response; }
According to your functions, if you want to redirect users when they are visiting the website’s homepage. You could implement the is_front_page() function to detect and only redirects if they are on the frontpage. function user_homepage() { if ( is_user_logged_in() ) { $args = array( ‘field’ => 25, ); $user_homepage = bp_profile_field_data( $args ); if … Read more
You are using the wrong meta key: update_user_meta( $user_id, ‘Save Posts’, $_POST[‘save_post_external’] ); update_user_meta( $user_id, ‘Save Posts’, $_POST[‘save_post_internal’] ); And that should be: update_user_meta( $user_id, ‘save_post_external’, $_POST[‘save_post_external’] ); update_user_meta( $user_id, ‘save_post_internal’, $_POST[‘save_post_internal’] );
Is there a smart way to meta_query so it matches just “IS, but not “TS-IS”? The WordPress meta query class (WP_Meta_Query), which among others, is used with the posts (WP_Query) and users (WP_User_Query) query classes, supports REGEXP (since WordPress 3.7) as the compare value, so you could use that with a RegEx (regular expresion) pattern … Read more