This is happening to me on several sites as well. Here is an example of a shortcode I created in function.php of the child theme which gave me trouble after the update:
function get_home_recent_posts() {
$args = array(
'post_type' => 'post',
'posts_per_page' => '3',
'orderby' => 'DESC',
'offset' => '1',
);
// The Query
$the_query = new WP_Query( $args );
// The Loop
if ( $the_query->have_posts() ) {
echo '<div class="recent-post-box boxfix">';
echo '<div class="clearfloat"></div>';
while ( $the_query->have_posts() ) {
$the_query->the_post();
if ( has_post_thumbnail() ) :
echo '<div class="recent-posts">';
echo '<a href="' . get_the_permalink() . '">';
the_post_thumbnail( 'medium', array( 'class' => 'home-featured-img' ) );
echo '<h2>'. get_the_title() . '</h2>';
echo '</a>';
echo '</div><!-- /recent-posts -->';
endif;
}
echo '<br class="clearfloat" />';
echo '</div><!-- /recent-post-box -->';
}
/* Restore original Post Data */
wp_reset_postdata();
}
add_shortcode( 'home-recent-posts', 'get_home_recent_posts' );
As you can see, this is nothing fancy, just a simple little loop to grab some recent posts. The shortcode was implemented within the builder using the old Content Area element from a few versions back - before V2 elements even existed. After updating to 4.3.2 from 4.2.3 this broke everything. The posts were outputting above the header and the display was massively jacked up in general. This happened on several sites and was really not fun to deal with…
How I fixed it (some of the time):
Simply implemented the shortcode in a V2 text element instead and deleted the old Content Area. I even tried to use the newer Raw Content element with limited success. But the Text element seemed to work in the majority of cases.
The still very weird and concerning thing:
One of these sites does not use any custom shortcodes. But it does make use of the plugin The Grid. The grid element inserted in the builder is a shortcode of course but it is not custom. It is how this has always worked. Just paste it into a Content Area element and The Grid you build in the plugin is displayed (well, in the front end, the builder always has trouble - that is not what I am talking about here).
On this site however, changing to a text element made no difference at all. The site was just as messed up after doing that. Again, not awesome.
Conclusions:
Something has changed fundamentally about the way these shortcodes are being executed from inside elements since the last release. The code we are implementing was put in place by a developer we already hired - that’s how it got there to begin with (in my case, it was me personally but other’s may have outsourced help and paid for that already to be working). It is not acceptable to suggest that we need to hire a developer to fix what got broken from software you pushed out when it has worked literally the entire time before. In other words, the problem is not with the shortcodes (or functions they call when executed) but rather with the way Pro is handling them after an update. It is incumbent on you guys to address that in some way because, as I’ve said, this is not isolated to custom programming. The Grid is out of whack in some cases too, as in my example.
What can you tell us about your plans to address this issue? It is pretty urgent as you can imagine.
Thanks in advance.
