WebMan Design | Oliver Juhas

<p>Extending WordPress Navigation block with functionality to display classic menus.</p>
<h4>What problem does it solve?</h4>
<p>❓ <em>Do you experience problems making your website navigation multilingual when using block theme (FSE – full site editing)?</em><br />
❓ <em>Are you using a plugin that modifies classic menu but not Navigation block and you are using block theme?</em></p>
<p><strong>Classic Menu in Navigation Block</strong> plugin lets you display classic menus in Navigation block so you can gain from using classic menu modification plugins and yet display the menu with accessibility, customization and responsive features of Navigation block.</p>
<p>This method is particularly useful when building a multilingual website and your multilingual plugin does not handle Navigation block very well. You can simply “revert” back to using classic menu, which multilingual plugins supports out of the box.</p>
<p>You can do changes to your classic menus and Navigation block will always display up to date version of the menu.</p>
<p>To speed things up the plugin also applies caching for your classic menus converted to blocks. This cache is updated every time you update your classic menu. If you are using a very dynamic classic menu modification plugin, you can even disable the cache.</p>
<h4>Got a question or suggestion?</h4>
<p>In case of any question or suggestion regarding this plugin, feel free to ask at <a href="https://wordpress.org/support/plugin/classic-menu-in-navigation-block/" rel="ugc">support section</a>, or at <a href="https://github.com/webmandesign/classic-menu-in-navigation-block/issues" rel="nofollow ugc">GitHub repository issues</a>.</p>


Classic Menu in Navigation Block


Great job, maybe needed some polishing, but it provides exactly that is needed. Gives the Classic Menu Admin and ability to style.



It would be great to see the classic menu working on the edit mode when the menu is selected, otherwise it is a little confusing, is it selected or not.


Exactly what needed


Great to add that classic control when using an FSE theme.


Worked like a dream

Extending WordPress Navigation block with functionality to display classic menus.

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  …

Classic Menu in Navigation Block vs Content Area Block