WordPress plugin intelligence profile

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 …

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.0
Current version1.0.3
WordPress coverageTested up to WordPress 7.0
Minimum stackWP 6.7 · PHP 7.4
Directory statusactive
Last directory update9 Jul 20263mo ago
Active installations10Adoption metric — not a quality score
WordPress.org rating5.0 / 5 from 2 ratings
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Content Area Block version 1.0.3 as active, updated 3mo ago and tested up to WordPress 7.0.

Overview

About this plugin

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.

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!

Requirements

  • 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.
  • 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).

Hooks

If you want to disable this meta key’s registration, add the following to your theme or plugin:

php add_filter( 'content_area_block_register_default_meta', '__return_false' );

For advanced users, there is also a filter for the entire block’s output. php:

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( ']]>', ']]>', $content ) ), $block_post_id, $attributes, $content, $block );

Contributing

com/iansvo/content-area-block.

To build the plugin from source, you must have NodeJS (v24+) installed.

Setup Steps:

  • Navigate to the project folder in your terminal.
  • Run npm i to install dependencies.
  • Run npm run build to performn the initial build.

If you’re using wp-env to run the plugin…

1. Run npm run wp-env start to start the docker container.

2. Run npm run start to watch for file changes.

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • site editor
  • block
  • content
  • fse
  • template
Compatibility & maintenance

Compatibility & maintenance

Tested up to WordPress 7.0

Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 7.0.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.0
Minimum requirementsWordPress 6.7 · PHP 7.4
Update activity9 Jul 20263mo ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.