partage-it

<p>WP atomic content allows to create content blocks to use in posts, pages and custom post types.</p>
<h4>Getting started</h4>
<ol>
<li>create a new block in the WordPress admin interface (in the block menu), write some contents and publish it</li>
<li>copy the suggested shortcode</li>
<li>in a page, post, or whatever, paste the shortcode where you want to see the block’s content</li>
<li>you’re done</li>
</ol>
<h4>The shortcode, basically</h4>
<pre><code>[block id="my-block-name"]
</code></pre>
<p>This shortcode includes the content of the <code>my-block-name</code> block in the page.</p>
<p>If the block is not found, nothing happens, no errors, no additional spaces. Nothing.</p>
<h4>Spaced content</h4>
<pre><code>[block id="my-block-name" spacebefore="1em" spaceafter="30px" /]
</code></pre>
<p>It is possible to set space before and after the content with <code>spacebefore</code> and <code>spaceafter</code> shortcode parameters.</p>
<p>Units are CSS compatible, so feel free to use <code>px</code>, <code>em</code>, <code>rem</code>, <code>cm</code>, …</p>
<h4>Custom CSS classes</h4>
<pre><code>[block id="my-block-name" class="my-class"]
</code></pre>
<p>Adding the <code>class</code> parameter, the CSS class is added to the block, in order to customize it.</p>
<p>It is possible to set many classes, with a space as separator.</p>
<p>You should note that two classes, <code>atomic-content-block</code> and <code>block-<id></code>, are added to every included blocks, without any customization.</p>
<p>Moreover, an identifier is added, to easily link the block with anchors (<code>id="<id>"</code>).</p>
<h4>Block content</h4>
<p>The block editor is the same as the post editor. In other words, it is possible to format content (add paragraphs, titles, …).</p>
<p>It is also possible to add shortcodes, even to include blocks.</p>
<p>So you can make blocks composed of blocks, but be careful to not make cyclic references (<code>a</code> includes <code>b</code> which includes <code>a</code>).</p>
<h4>PHP use</h4>
<p>You can include blocks from PHP code (i.e. in theme or plugin code), without shortcode.</p>
<p>The PHP functions, named <code>atomicContent</code> works like the shortcode, with the same parameters.</p>
<p>The signature:</p>
<pre><code>string atomicContent($id, $classes = array(), $spaceBefore = null, $spaceAfter = null, $display = true)
</code></pre>
<p>When <code>$display</code> is <code>true</code>, the result is directly displayed. Otherwise it is returned as result of the function.</p>
<p>Sample:</p>
<pre><code>atomicContent("my-block-name", array("my-class"), "1em", "30px")
</code></pre>


WP atomic content

WP atomic content allows to create content blocks to use in posts, pages and custom post types.

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

Prevent broken shortcodes from appearing in posts and pages.

WP atomic content vs Hide Broken Shortcodes