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.

This plugin provides the functions <code>c2c_if_file_exists()</code>, <code>c2c_if_theme_file_exists()</code>, <code>c2c_if_plugin_file_exists()</code> that check if a file exists and either return true/false or display a string containing information about the file.
<ul>
<li>If a format string is not passed to it, the functions returns a simple boolean (true or false) indicating if the specified file exists.</li>
<li>Otherwise, the format string provided to it will be used to construct a response string, which can be customized to display information about the file (such as directory, extension, name, path, size, or url). If the <code>$echo</code> argument is true, that string is displayed on the page. Regardless of the value of <code>$echo</code>, the response string is returned by the function.</li>
</ul>
By default, <code>c2c_if_file_exists()</code> assumes you are looking for the file relative to the default WordPress upload directory. If you wish to search another directory, specify it as the <code>$dir</code> argument. <code>c2c_if_theme_file_exists()</code> assumes you are looking for a file relative to the currently active theme’s home directory. <code>c2c_if_plugin_file_exists()</code> assumes you are looking for a file relative to the directory that contains WordPress plugins.
Links: <a href="https://coffee2code.com/wp-plugins/if-file-exists/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/if-file-exists/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/if-file-exists/" 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/if-file-exists/blob/master/DEVELOPER-DOCS.md" rel="nofollow ugc">DEVELOPER-DOCS.md</a>. That documentation covers the template tags and hooks provided by the plugin.
As an overview, these are the template tags provided by the plugin:
<ul>
<li><code>c2c_if_file_exists()</code> : Checks if a file exists and returns true/false or displays a string containing information about the file.</li>
<li><code>c2c_if_plugin_file_exists()</code> : Checks if a file exists (relative to the plugins directory) and returns true/false or displays a string containing information about the file.</li>
<li><code>c2c_if_theme_file_exists()</code> : Checks if a file exists (relative to the current theme’s directory) and returns true/false or displays a string containing information about the file. If the current theme is a child theme, then the function will check if the file exists first in the child theme’s directory, and if not there, then it will check the parent theme’s directory.</li>
</ul>
These are the hooks provided by the plugin:
<ul>
<li><code>c2c_if_file_exists</code> : Filter that allows use of an alternative approach to safely invoke <code>c2c_if_file_exists()</code> in such a way that if the plugin were deactivated or deleted, then your calls to the function won’t cause errors in your site.</li>
<li><code>c2c_if_plugin_file_exists</code> : Filter that allows use of an alternative approach to safely invoke <code>c2c_if_plugin_file_exists()</code> in such a way that if the plugin were deactivated or deleted, then your calls to the function won’t cause errors in your site.</li>
<li><code>c2c_if_theme_file_exists</code> : Filter that allows use of an alternative approach to safely invoke <code>c2c_if_theme_file_exists()</code> in such a way that if the plugin were deactivated or deleted, then your calls to the function won’t cause errors in your site.</li>
</ul>

If File Exists

Check if a file exists and return true/false or display a string containing information about the file.

Hide Broken Shortcodes vs If File Exists