Scheduled Posts Showcase

Scheduled Posts Showcase lets you display your scheduled (future) posts on the frontend of your WordPress site without creating problematic links to unpublished content. Unlike other solutions that link to scheduled posts and generate 404 errors for visitors, this plugin shows post information (title, date, excerpt, featured image, categories) without ever exposing the permalink or post ID. Key Features

• No 404 errors - Never generates links to unpublished content
• Multiple display methods - Use shortcode, widget, Gutenberg block, or REST API
• Fully customizable - Control what information to display and how it looks
• Global settings with per-instance overrides - Set defaults once, customize where needed
• Translation ready - Fully prepared for localization
• Developer friendly - Extensive hooks for customization

Display Options

• Number of posts to show
• Featured image at any registered size, including a responsive "full width" option that fills the container
• Scheduled publication date
• Post excerpt (with configurable word count)
• Categories
• Custom heading with selectable HTML tag (headings, paragraph, span or div)
• Custom footer content for calls to action
• Custom CSS classes on the main container, both globally and per instance

Appearance Options

• Card or minimal container style
• Dashicon, theme default, or no list bullets
• Curated icon selector for list bullets
• Accent color customization
• Responsive design

Visibility Control Choose who can see your scheduled posts:

• Everyone (public)
• Logged-in users only
• Editors and administrators only

Usage Shortcode: [scheduled-posts-showcase] With parameters: [scheduled-posts-showcase count="3" show_date="1" show_excerpt="1" container_style="card"] Widget: Add the "Scheduled Posts Showcase" widget to any widget area from Appearance → Widgets. Gutenberg Block: Search for "Scheduled Posts" in the block inserter and add the block to any post or page. REST API: GET /wp-json/scheduled-posts-showcase/v1/scheduled-posts Parameters: per_page, fields, post_type, order Why This Plugin? Existing plugins for displaying scheduled posts either:

• Are abandoned (some over 10 years old)
• Link to scheduled posts, causing 404 errors
• Use deprecated WordPress functions
• Lack modern features like Gutenberg blocks

Scheduled Posts Showcase solves all these problems with a modern, secure, and fully-featured solution.

1.2.0

• New: heading tag options for paragraph, span and div in addition to H2-H6.
• New: "Custom CSS class" field on the settings page. Adds extra classes to every instance container (widget, block, shortcode).
• New: "Extra CSS class" field on the widget, the block inspector and as custom_class shortcode attribute. Per-instance classes are appended to the global ones, never replace them.
• New: "Full width (responsive)" image size that stretches the thumbnail to the container width, useful for sidebar hero-style cards.
• New: spscase_heading_tags and spscase_image_sizes filters to extend those lists from code.
• Improved: settings page moved to Appearance > Future Posts instead of Tools, since the plugin is mostly about visual display. The page slug is unchanged so existing bookmarks pointing to ?page=scheduled-posts-showcase still work.
• Improved: image size selector now lists every size registered on the site (themes and plugins included) instead of just thumbnail and medium.
• Improved: clearer help text on the CSS class fields. They add the class name to the container; the CSS itself still has to live in your theme or in Customize > Additional CSS.
• Improved: promo catalog on the settings sidebar updated with the latest AyudaWP plugins, including the rest of the Native SEO Suite, and small visual fixes aligned with the AyudaWP banner guide.
• Fix: the block preview no longer fails in the block-based widgets editor. The editor script now declares wp-server-side-render as an explicit dependency via a companion .asset.php file, which the widgets editor was not pulling in transitively (resulting in a React #130 error). For older changelog entries, please check the changelog.txt file