santiagodel76

<p>Timed Event Block adds a server-rendered parent block for scheduling event content by date/time, plus dedicated child blocks for dynamic date, time, and countdown output.</p>
<p>Ideal for event listings such as movie showtimes, class schedules, workshops, conferences, livestreams, and similar use cases. It requires no global configuration: install the plugin and start using the block directly in FSE workflows.</p>
<p>This plugin is designed for full site editing workflows where content creators need:</p>
<ul>
<li>A single event container that can hold any core block (text, media, embeds, columns, groups, etc.).</li>
<li>Automatic status handling based on current server time:</li>
<li>Scheduled</li>
<li>Active</li>
<li>Ended</li>
<li>Optional automatic hiding of ended events (<code>Hide when ended</code>).</li>
<li>Child blocks that can be used only inside the Timed Event parent:</li>
<li>Event Date</li>
<li>Event Time</li>
<li>Event Countdown</li>
<li>Dynamic frontend updates for status/time/countdown without page refresh.</li>
<li>Native Gutenberg style controls (spacing, color, typography, border, dimensions) on parent and child blocks.</li>
</ul>
<p>How it works:</p>
<ol>
<li>Add a <strong>Timed Event</strong> block.</li>
<li>Set start date/time and duration.</li>
<li>Insert any content you want.</li>
<li>Optionally insert child blocks:</li>
</ol>
<p>* <strong>Event Date</strong> for date display with site/custom format.<br />
* <strong>Event Time</strong> for scheduled time and active/ended label transitions.<br />
* <strong>Event Countdown</strong> for countdown to start/end and status transitions.<br />
5. Publish. Frontend output is resolved server-side, and dynamic text updates via lightweight view scripts.</p>
<h3>Blocks</h3>
<h4>Timed Event</h4>
<p>Parent container block that controls event lifecycle and visibility.</p>
<p>Features:<br />
* Start date and time.<br />
* Duration in minutes.<br />
* Hide when ended toggle.<br />
* Full inner content flexibility.</p>
<h4>Event Date</h4>
<p>Child block (ancestor-restricted to Timed Event) that reads parent context and renders formatted date.</p>
<p>Features:<br />
* Site default format or custom format string.<br />
* Uses WordPress timezone and date settings by default.</p>
<h4>Event Time</h4>
<p>Child block that reads parent context and renders:<br />
* Scheduled state: formatted time.<br />
* Active state: configurable active label.<br />
* Ended state: configurable ended label.</p>
<p>Features:<br />
* Site/custom time format.<br />
* Editable active/ended labels.<br />
* Editable active/ended colors.<br />
* Dynamic frontend state update.</p>
<h4>Event Countdown</h4>
<p>Child block that reads parent context and renders:<br />
* Countdown to start or countdown to end.<br />
* Active/ended label after countdown completion.</p>
<p>Features:<br />
* Target mode: <code>to_start</code> or <code>to_end</code>.<br />
* Day visibility toggle.<br />
* Custom separator.<br />
* Editable active/ended labels.<br />
* Editable active/ended colors.<br />
* Dynamic frontend state update.</p>


Timed Event Block

Schedule event visibility and create flexible event layouts with native Gutenberg blocks for modern WordPress editing workflows.

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  …

Timed Event Block vs Content Area Block