santiagodel76

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.
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.
This plugin is designed for full site editing workflows where content creators need:
<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>
How it works:
<ol>
<li>Add a Timed Event block.</li>
<li>Set start date/time and duration.</li>
<li>Insert any content you want.</li>
<li>Optionally insert child blocks:</li>
</ol>
* Event Date for date display with site/custom format. 
* Event Time for scheduled time and active/ended label transitions. 
* Event Countdown for countdown to start/end and status transitions. 
5. Publish. Frontend output is resolved server-side, and dynamic text updates via lightweight view scripts.
<h3>Blocks</h3>
<h4>Timed Event</h4>
Parent container block that controls event lifecycle and visibility.
Features: 
* Start date and time. 
* Duration in minutes. 
* Hide when ended toggle. 
* Full inner content flexibility.
<h4>Event Date</h4>
Child block (ancestor-restricted to Timed Event) that reads parent context and renders formatted date.
Features: 
* Site default format or custom format string. 
* Uses WordPress timezone and date settings by default.
<h4>Event Time</h4>
Child block that reads parent context and renders: 
* Scheduled state: formatted time. 
* Active state: configurable active label. 
* Ended state: configurable ended label.
Features: 
* Site/custom time format. 
* Editable active/ended labels. 
* Editable active/ended colors. 
* Dynamic frontend state update.
<h4>Event Countdown</h4>
Child block that reads parent context and renders: 
* Countdown to start or countdown to end. 
* Active/ended label after countdown completion.
Features: 
* Target mode: <code>to_start</code> or <code>to_end</code>. 
* Day visibility toggle. 
* Custom separator. 
* Editable active/ended labels. 
* Editable active/ended colors. 
* Dynamic frontend state update.

Timed Event Block

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

Sébastien SERRE

Emmanuel Hesry

hugod

This plugin, usable only with a block theme like Twenty Twenty-Two, adds the legacy widgets block in the Site Editor (FSE).
With the legacy widgets block, you can use the legacy widgets as Navigation Menu for example.
This is why this plugin reintroduces the WordPress legacy Menus screen to be able to manage menus you want to use with the Navigation Menu widget.
This also allows to use external plugins legacy widgets which might not have already been converted to blocks.

Site Editor Classic Features


After fiddling around a bit I got working.



You have to use the legacy widgets -> navigation menu


Still works in 2024

Make legacy widgets and menus usable in Site Editor (FSE).

Timed Event Block vs Site Editor Classic Features