WordPress'es support for future events assumes that the only person who can see them is the author. It all stems back to when WordPress was just a blog. You could write a load of posts and schedule them to appear on the publication date. But what if you are a club and need to publish future events. Well there are hundreds of plugins related to Events. Some of them are very popular. But they are also a big overhead when all you need is the ability to indicate when the event is.

I've developed a number of bespoke solutions that deal with events:

• Fixtures - for RNGS - using https://github.com/bobbingwide/oik-types and https://github.com/bobbingwide/oik-fields
• Events for TAGS - https://github.com/bobbingwide/tags
• Meetups for WP-Pompey - https://github.com/wppompey/wppompey

Each of these used a Custom Post Type ( CPT ) with a custom field that stored the event date.

I already knew that I could display the future content using a shortcode.

[bw_table post_type='post' post_status='future' fields=title,post_status,post_date orderby=date order=desc]

But clicking on the link only displayed the content when I was logged in.

I wondered how easy it would be to create future events either as Posts or Pages which would be visible to other site users.

I started a new plugin ( called oik-future) and wrote under 10 lines of code.

When the plugin's loaded then call this initialisation routine

oik_future_loaded();

Add an action to hook into the query

function oik_future_loaded() {
	add_action( 'pre_get_posts', 'oik_future_pre_get_posts' );
}

If the query is the main query then change it to load Scheduled ( future) posts as well as Published ( publish ).

function oik_future_pre_get_posts( $query ) {
	if ( $query->is_main_query() ) {
		$query->set( 'post_status', ['publish', 'future']);
	}
}

And lo and behold I was able to see the future events even when not logged in.

Here's the table of events...

And here's the first post viewed in Firefox, by a non logged in user.

Well that wasn't hard. Now what?

Requirements

• To create events in the future
• To display a list of future events
• To be able to view each event
• Regardless of user type
• Event list to be automatically updated on date change
• Future events to include the current date?
• Display fields such as Title (as a link ), publication date, excerpt, read more

Proposed solution

• Develop a block called oik-sb/coming-up
• that will server side render the equivalent of the bw_pages / bw_table shortcode
• With styling of the date to be similar to Events plugins
• Add support to display posts with post status future to any site visitor.

This is the same problem as noted in bobbingwide/bobbingwide#30 (comment)
It occurs for the sb-coming-up block which uses server side rendering to render the posts.
The block works in the Widgets block editor.
But there's a Notice due to the block's dependency on wp-editor

The Coming Up block wasn't developed with the Widget block editor in mind.
It works fine in a FSE theme, where widget areas no longer exist as entities.
But now that the Widget block editor is here then, along with many other blocks developed pre Widget block editor era, this block should also be capable of operating in widget areas.

The trouble is, apart from removing the hook that's producing the Notice ( see the referenced comment), I have no idea how to resolve the problem.

In my opinion I'm doing nothing wrong.
It's core that's not worked out how to deal with it, and it's passing the buck.
Either the core code needs changing OR a very clear set of Field notes are needed.

See also WordPress/gutenberg#33443