iansvo

<p>This block allows you to add an additional block content area to a site-editor template and store the block output inside a meta field. By default, WordPress posts or pages may only store blocks in one place: post_content. These blocks are output on the page using the core/post-content block. This block allows you to have multiple “outlets” where you can add blocks so you can have post-specific blocks appear in more than one location in the template.</p>
<p>The block is a fork of the core/post-content block that uses a customized version of the useEntityBlockEditor hook which supports meta keys. The blocks for your content area are then stored inside that meta key (instead of post_content). This allows you to keep the blocks separate and you can use as many of these on a single template as you want (but in most cases 2 is probably enough). It’s all up to you!</p>
<h3>Requirements</h3>
<ol>
<li>Using this plugin requires you to enable template previews (which will let you visually see the new content area you’re adding). This can be enabled on any given post or page, but you can optionally set it on by default using a filter.</li>
<li>Your theme must be a block theme (i.e. it uses the site editor). This won’t work for a hybrid or classic theme (which has no concept of live template preview in the block editor).</li>
</ol>
<h3>Hooks</h3>
<p>If you want to disable this meta key’s registration, add the following to your theme or plugin:</p>
<pre><code><?php
add_filter( 'content_area_block_register_default_meta', '__return_false' );
</code></pre>
<p>For advanced users, there is also a filter for the entire block’s output. See the below snippet from render.php:</p>
<pre><code><?php
/**
 * Filter the block's frontend output.
 *
 * @param string $parsed_content The parsed block content for output.
 * @param int    $block_post_id  The current post ID the block is displaying in.
 * @param array  $attributes     The block attributes.
 * @param string $content        The original unparsed block content.
 * @param object $block          The current parsed block object.
 *
 * @return The block content for output on the frontend.
 */
$output = apply_filters( 
    'content_area_block_content', 
    do_blocks( str_replace( ']]>', ']]&gt;', $content ) ), 
    $block_post_id, 
    $attributes, 
    $content, 
    $block 
);
</code></pre>
<h3>Contributing</h3>
<p>The plugin source code may be found here: https://github.com/iansvo/content-area-block.</p>
<p>To build the plugin from source, you must have NodeJS (v24+) installed.</p>
<p>Setup Steps:</p>
<ol>
<li>Navigate to the project folder in your terminal.</li>
<li>Run <code>npm i</code> to install dependencies.</li>
<li>Run <code>npm run build</code> to performn the initial build.</li>
</ol>
<p>If you’re using wp-env to run the plugin…<br />
1. Run <code>npm run wp-env start</code> to start the docker container.<br />
2. Run <code>npm run start</code> to watch for file changes.</p>


Content Area Block

Adds a block content area to a site editor template and stores the blocks in a specified meta field. By default, the plugin will add a new meta field  …

Shaan

<p>This plugin adds a set of new search results to the WordPress command palette (CMD+K/CTRL+K) for all entries from registered types, and thus, enables quick jumps through all posts and pages which are not limited to the built-in Post and Page types.</p>
<p>WordPress has a great time-saving feature— the command palette. Before WordPress v6.9, the command palette was available only in the editor. Since WordPress v6.9, the command palette is available anywhere inside the admin area. It is quite useful to perform quick commands and navigate through pages or posts using keyboard alone. However, it is limited to the core Post and Page types. It does not populate entries from user customized types. So, for the users of Custom Post Types, this workflow that partially breaks due to the absense of custom post types.</p>
<p>This plugin fills up this gap in WordPress core. It injects those missing <strong>Custom Post Type</strong> entries into the command palette. It requires no complex setup. Just install, activate and it is ready to go!</p>
<p>If you find this plugin useful, then please leave an appropriate review.</p>
<h3>Configuration</h3>
<p>See <strong>Settings</strong> <span aria-hidden="true" class="wp-exclude-emoji">→</span> <strong>CPT Commands</strong> for customization options. This step is optional and not necessary in most cases.</p>


CPT Commands


Such a great plugin!Just install and activate and your custom post types are automatically added to the command palette.



I love that the settings page includes a list of custom post types that you can simply check a box to exclude.


Works perfectly with zero setup

Adds a set of new search results to the WordPress command palette (CMD+K/CTRL+K) for all entries from registered Custom Post Types.

Content Area Block vs CPT Commands