To make sure the shortcode executes, save the content to a variable, then run do_shortcode on the saved variable. <div class=”thecontent” itemprop=”articleBody”> <?php $content = get_the_content(); echo do_shortcode($content); ?> </div> The difference is, echoing just literally echoes whatever has been grabbed. PHP’s built-in functions don’t have any special way to process shortcodes so they just … Read more
Don’t use the_post, instead use the_content filter to modify content passed to the the_content() call. However, this is your theme, so the best way to do this is to just do it in search.php, and not bother with the filters and actions. AKA don’t run the code on a filter to try and modify or … Read more
change the_ID() to get_the_ID(). calling the_ID() prints the post’s ID, while get_the_ID() simply returns it and allows you to use it further on. reference : get_the_ID()
I may be misinterpreting you, but I think what you want to do is run through strip_shortcodes $page_data[‘content’] = strip_shortcodes($page->post_content); $page_data[‘content’] = apply_filters(‘the_content’, $page_data[‘content’]); Alternately you could conditionally hook that function to the_content as demonstrated on the Codex Page.
There’s a few things you need to do here, you need to modify your add_action() to accept additional arguments and you need to specify whether to use the data before the update or the data after the update. Try something like this: function send_media_emails($post_id, $post_after){ if(defined(‘DOING_AUTOSAVE’) && DOING_AUTOSAVE) return; if(get_post_status($post_id) == ‘draft’ or get_post_status($post_id) == … Read more
This can be done using the blocks.getSaveElement filter as shown in the example below. I would STRONGLY caution that this has the potential for bad times. Core blocks are static blocks. This means that the output is saved to the database. If you want to remove these spans, you’ll need to basically redo all of … Read more
Not automatically. You don’t know a filter exists until something tries to add it or runs it, and you have no guarantee what that filter is for without docs or a human being to describe it. You can do this by hand for core itself as it’s well documented what the filters are, but there … Read more
You’re using query_posts() for your featured-post custom loop. As the Codex says: don’t do that. The query_posts() function is intended to modify the Primary Loop. If you need a custom loop, use e.g. $my_custom_query = new WP_Query( $args ). See here for a good break-down of custom-loop options.
If $content_width is the problem, you could set it to something different if you’re viewing a single HQ post. function wpse99587_single_hq_post() { global $post; if( is_single() && in_category( ‘HQ’, $post->ID ) ){ global $content_width; $content_width = 900; } } add_action( ‘wp’, ‘wpse99587_single_hq_post’ ); // I dithered on where to hook this function; // if there’s … Read more
I worked it out and re-wrote the code: jQuery(document).ready(function() { jQuery(‘#createacostume’).submit(function( event ) { event.preventDefault(); var aForm = jQuery(this); var bForm = aForm.serializeArray(); bForm.push({name: ‘action’, value: ‘myAjaxFunction’}); jQuery.ajax({ url: ajaxurl, type: “POST”, data: bForm, success: function(resp) { alert(“Thank you for your post. We will review it and approve it shortly” + resp); }, error: function( … Read more