Scott Reilly

<p>By default in WordPress, if the plugin that provides the functionality to handle any given shortcode is disabled, or if a shortcode is improperly defined in the content (such as with a typo), then the shortcode in question will appear on the site in its entirety, unprocessed by WordPress. At best this reveals unsightly code-like text to visitors and at worst can potentially expose information not intended to be seen by visitors.</p>
<p>This plugin prevents unhandled shortcodes from appearing in the content of a post or page. If the shortcode is of the self-closing variety, then the shortcode tag and its attributes are not displayed and nothing is shown in their place. If the shortcode is of the enclosing variety (an opening and closing tag bookend some text or markup), then the text that is being enclosed will be shown, but the shortcode tag and attributes that surround the text will not be displayed.</p>
<p>See the Filters section for more customization tips.</p>
<p>Links: <a href="https://coffee2code.com/wp-plugins/hide-broken-shortcodes/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/hide-broken-shortcodes/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/hide-broken-shortcodes/" rel="nofollow ugc">GitHub</a> | <a href="https://coffee2code.com" rel="nofollow ugc">Author Homepage</a></p>
<h3>Developer Documentation</h3>
<p>Developer documentation can be found in <a href="https://github.com/coffee2code/hide-broken-shortcodes/blob/master/DEVELOPER-DOCS.md" rel="nofollow ugc">DEVELOPER-DOCS.md</a>. That documentation covers the hooks provided by the plugin.</p>
<p>As an overview, these are the hooks provided by the plugin:</p>
<ul>
<li><code>hide_broken_shortcode</code>          : Customizes what, if anything, gets displayed when a broken shortcode is encountered.</li>
<li><code>hide_broken_shortcodes_filters</code> : Customizes what filters to hook to find text with potential broken shortcodes.</li>
</ul>


Hide Broken Shortcodes

This plugin does what it says. Really a great plugin. Thank you developer.

Works Great!

Prevent broken shortcodes from appearing in posts and pages.

<p>A widget that can act as a duplicate of another widget (for synchronized use in another sidebar)</p>
<p>Define a widget once, use it in multiple sidebars.  This saves you from having to manually configure each copy of the widget and later having to worry about keeping them in sync should you ever need to make any changes.  Particularly useful for those who define logic in their themes to conditionally include different versions of a sidebar depending on what template is being shown. Depending on use, it is an alternative to plugins that introduce in-widget logic to determine when widgets should be visible (Widget Logic, Section Widget, Conditional Widgets, etc).</p>
<p>Quick overview of what this plugin does:</p>
<ul>
<li>Adds a widget called “Duplicate”. The widget’s only setting is a dropdown listing all active widgets.  The selected widget will be the widget duplicated by the duplicate widget.</li>
<li>A duplicate widget shows the same title and content as its source widget, even if those values later get changed in the source widget.</li>
<li>A widget can be duplicated any number of times and can appear multiple times within the same page. (Yes, even within the same sidebar, though why would you do that?)</li>
<li>A duplicate widget will abide by the configuration of the sidebar it is placed in, not the configuration of the sidebar containing the source widget.  So it uses ‘before_widget’, ‘after_widget’, ‘before_title’, ‘after_title’ values of its own sidebar.</li>
<li>Widgets that are duplicated will have “[D]” prepended to their name in the widget titlebar in the admin to denote they have duplicates.  Also, at the bottom of the widget’s configuration form (when the widget is expanded), a short blurb also explains that the widget has duplicate(s) and a count of how many duplicates it has.</li>
<li>If a widget is deactivated or deleted, if it has any duplicates, they get deleted as well.</li>
<li>The widget id and widget type of the source widget are included as HTML classes in the duplicate widget’s markup.</li>
</ul>
<p>Links: <a href="http://coffee2code.com/wp-plugins/duplicate-widget/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/extend/plugins/duplicate-widget/" rel="ugc">Plugin Directory Page</a> | <a href="http://coffee2code.com" rel="nofollow ugc">Author Homepage</a></p>
<h3>Filters</h3>
<p>The plugin exposes four actions for hooking.  Typically, customizations utilizing these hooks would be put into your active theme’s functions.php file, or used by another plugin.</p>
<h4>c2c_before_duplicate_widget (action)</h4>
<p>The ‘c2c_before_duplicate_widget’ hook allows you to output text, or perform some sort of action, just before the output of the duplicate widget.</p>
<p>Arguments:</p>
<ul>
<li>$instance (array) : The settings for the widget instance (namely: title and widget_to_duplicate)</li>
<li>$args (array) : The configuration for the widget and sidebar</li>
</ul>
<p>Example:</p>
<pre><code>// Output an opening <div> before duplicate widget content
add_action( 'c2c_before_duplicate_widget', 'my_c2c_before_duplicate_widget', 10, 2 );
function my_c2c_before_duplicate_widget( $instance, $args ) {
    echo '<div class="a_duplicate_widget">;
}
</code></pre>
<h4>c2c_after_duplicate_widget (action)</h4>
<p>The ‘c2c_after_duplicate_widget’ hook allows you to output text, or perform some sort of action, just after the output of the duplicate widget.</p>
<p>Arguments:</p>
<ul>
<li>$instance (array) : The settings for the widget instance (namely: title and widget_to_duplicate)</li>
<li>$args (array) : The configuration for the widget and sidebar</li>
</ul>
<p>Example:</p>
<pre><code>// Output an closing </div> after duplicate widget content
add_action( 'c2c_after_duplicate_widget', 'my_c2c_after_duplicate_widget', 10, 2 );
function my_c2c_after_duplicate_widget( $instance, $args ) {
    echo '</div>;
}
</code></pre>
<h4>c2c_before_duplicate_widget_form (action)</h4>
<p>The ‘c2c_before_duplicate_widget_form’ hook allows you to output text, or perform some sort of action, just before the output of the duplicate widget’s configuration form (in the WP admin).</p>
<p>Arguments:</p>
<ul>
<li>$instance (array) : The settings for the widget instance (namely: title and widget_to_duplicate)</li>
</ul>
<p>Example:</p>
<pre><code>// Display a message just before the duplicate widget settings form
add_action( 'c2c_before_duplicate_widget_form', 'my_c2c_before_duplicate_widget_form' );
function my_c2c_before_duplicate_widget_form( $instance ) {
    echo '<p>Note: this is a note above the widget settings form.</p>';
}
</code></pre>
<h4>c2c_after_duplicate_widget_form (action)</h4>
<p>The ‘c2c_after_duplicate_widget_form’ hook allows you to output text, or perform some sort of action, just after the output of the duplicate widget’s configuration form (in the WP admin).</p>
<p>Arguments:</p>
<ul>
<li>$instance (array) : The settings for the widget instance (namely: title and widget_to_duplicate)</li>
</ul>
<p>Example:</p>
<pre><code>// Display a message just after the duplicate widget settings form
add_action( 'c2c_after_duplicate_widget_form', 'my_c2c_after_duplicate_widget_form' );
function my_c2c_after_duplicate_widget_form( $instance ) {
    echo '<p>Note: this is a note below the widget settings form.</p>';
}
</code></pre>


Duplicate Widget

A widget that can act as a duplicate of another widget (for synchronized use in another sidebar)

Hide Broken Shortcodes vs Duplicate Widget