Scott Reilly

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.
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.
See the Filters section for more customization tips.
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>
<h3>Developer Documentation</h3>
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.
As an overview, these are the hooks provided by the plugin:
<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.

Reduce permalinks (category or post) that include entire hierarchy of categories to just having the lowest category in the hierarchy.
By default, WordPress replaces the %category% permalink tag in a custom permalink structure with the entire hierarchy of categories for the post’s first matching category. For example, assuming your site has a hierarchical category structure like so:
<pre><code>Applications
 |_ Desktop
 |_ Web
 |_ WordPress
</code></pre>
By default, if you have a permalink structure defined as <code>%category%/%year%/%monthnum%/%day%/%postname%</code>, your post titled “Best Plugins” assigned to the “WordPress” category would have a permalink of:
<pre><code>https://www.example.com/applications/web/wordpress/2008/01/15/best-plugins
</code></pre>
If you activate the Single Category Permalink plugin, this would be the permalink generated for the post (and recognized by the blog):
<pre><code>https://www.example.com/wordpress/2008/01/15/best-plugins
</code></pre>
In order for a category to be used as part of a post’s permalink structure, <code>%category%</code> must be explicitly defined in the Settings -> Permalinks admin page as part of a custom structure, i.e. <code>/%category%/%postname%</code>.
For category links, <code>%category%</code> is implied to follow the value set as the “Category base” (or the default category base if none is specified). So if your category base is ‘category’, the above example would list posts in the ‘WordPress’ category on this category listing page:
<pre><code>https://www.example.com/category/applications/web/wordpress/
</code></pre>
With this plugin activated, that link would become:
<pre><code>https://www.example.com/category/wordpress/
</code></pre>
NOTE: The fully hierarchical category and post permalinks will continue to work. The plugin issues a 302 redirect to browsers and search engines pointing them to the shorter URL.
Links: <a href="https://coffee2code.com/wp-plugins/single-category-permalink/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/single-category-permalink/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/single-category-permalink/" rel="nofollow ugc">GitHub</a> | <a href="https://coffee2code.com" rel="nofollow ugc">Author Homepage</a>
<h3>Hooks</h3>
The plugin exposes one filter for hooking. Code using this filter should ideally be put into a mu-plugin or site-specific plugin (which is beyond the scope of this readme to explain). Less ideally, you could put them in your active theme’s functions.php file.
c2c_single_category_redirect_status (filter)
The ‘c2c_single_category_redirect_status’ hook allows you to specify an HTTP status code used for the redirect. By default this is 302.
Arguments:
<ul>
<li>$status (integer) : The default HTTP status code</li>
</ul>
Example:
<pre><code>/**
 * Change the redirection HTTP status to a 302.
 *
 * @param int $code The HTTP status code. By default 301.
 * @return int
 */
function scp_change_redirect_status( $code ) {
 return 302;
}
add_filter( 'c2c_single_category_redirect_status', 'scp_change_redirect_status' );
</code></pre>

Single Category Permalink

Reduce permalinks (category or post) that include entire hierarchy of categories to just having the lowest level category.

Hide Broken Shortcodes vs Single Category Permalink