Using a leading underscore will hide the field’s value from the default WordPress Custom Fields section, not the meta box you create via the plugin. If you don’t want the field visible in your custom meta box, don’t add the field to the meta box at all, it really serves no purpose there anyway. You … Read more
Change the line <?php echo apply_filters(‘the_content’, get_post_meta($page->post_content, ‘custom_tagline’)); ?> to <?php echo apply_filters(‘the_content’, get_post_meta($page->ID, ‘custom_tagline’)); ?> See http://codex.wordpress.org/Function_Reference/get_post_meta
To connect your meta fields with the “Geo Data Store”-Plugin, you simply take the name of the meta key/field and map it with the filter to the plugin. add_filter( ‘sc_geodatastore_meta_keys’, ‘wpse82502_lat_lng_metakey_mapping’ ); function wpse82502_lat_lng_metakey_mapping( $keys ) { $keys[] = “your_meta_key_field_name”; return $keys; } To get the data from PHP to JS, simply use wp_localize_script().
Within Admin under ‘Screen Options’ tab, make sure ‘Custom Fields’ is ticked. Then below your Post you should find your Custom Fields area. From here, select the custom field from the dropdown and add content in the value field on the right. Hope this helps.
The solution was to simply wrap my JQuery in a function like this: $(‘#wpcontent’).ajaxStop(function() { $(‘.attachment-filters’).change(function(){ if($(this).val() === ‘uploaded’){ alert(“Uploaded images selected”); } else { alert(“Other option selected”); } }); });
You are using get_post_meta incorrectly, so it is returning FALSE every time. As PHP equates ‘0’ and FALSE, your div will always be displayed. The correct syntax for get_post_meta is: <?php $meta_values = get_post_meta($post_id, $key, $single); ?> where $post_id is the only required argument.
I’m not certain what an empty get_field returns, as it’s from a plugin. However, assuming it provides FALSE or an empty string: <?php $data = get_field( ‘data_nasterii’ ); echo ( $data ? date( “d/m/Y”, strtotime( $data ) ) : ‘N/A’ ); ?>
Unfiltered HTML in post content and title is a capability usually reserved for admins. If you don’t want to allow that for your users, don’t make them admins. Sanitation of custom fields has to be provided by the code author. There are use cases for such fields where entering JavaScript code is a desired feature. … Read more
Store site specific data in regular options. See add_option(), get_option() and so on. Store options for the complete network in a site option. See add_site_option() and related functions. You can add new fields for these options in a separate admin page or use an existing page for that. For the latter see my plugin Public … Read more
You just need to check for that custom field and return that instead of post content. function displayCustomContent() { if (!is_front_page()) return $content; // how to replace main post content with custom content ? global $post; $special_content = get_post_meta($post->ID,’page_builder’,true); if (!empty($special_content)) { // remove_all_filters(‘the_content’); return $special_content; } return $content; } The only other thing you … Read more