| 开发者 |
fernandot
ayudawp |
|---|---|
| 更新时间 | 2026年8月3日 07:53 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[scheduled-posts-showcase]
Without parameters it uses everything configured in Appearance → Scheduled Posts. With parameters:
[scheduled-posts-showcase count="3" show_date="1" show_excerpt="1" container_style="card"]
Filtering by content:
[scheduled-posts-showcase post_type="post,event" categories="news,tutorials" authors="fernando" tax_mode="include"]
post_type - one slug, a comma-separated list, or all for every public post typecategories and tags - term IDs or slugs, comma-separated, or all to skip that filtertax_<taxonomy> - any other taxonomy, for example tax_genre="fiction,essay"authors - user IDs or nicenames, comma-separated, or all to skip that filtertax_mode - include (default) or exclude[scheduled-posts-showcase categories="news"] keeps everything else as configured.
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 (comma-separated or all), order, categories, tags, taxonomy, terms, authors, tax_mode. Term and author parameters also accept all to skip that filter.
GET /wp-json/scheduled-posts-showcase/v1/scheduled-posts?post_type=post,event&categories=news&authors=12
Why This Plugin?
Existing plugins for displaying scheduled posts either:
/wp-content/plugins/scheduled-posts-showcase/ or install directly from the WordPress plugin repository.By design, this plugin never creates links to scheduled posts. Linking to unpublished content causes 404 errors for visitors, which is bad for user experience and SEO. Instead, the plugin shows post information to build anticipation without broken links.
Yes! Select any public post type from the settings page, or several at once, and specify them in the shortcode with post_type="your_post_type" or post_type="post,your_post_type".
Yes. The settings page has a "Content filters" section where you untick the "Any category" or "Any author" box and pick what you want, and decide whether the ticked terms are shown or hidden. Every widget, block and shortcode can override those filters with its own.
Each post type shows the terms of its own hierarchical taxonomies, and falls back to the flat ones when it has none. If you need a different set, use the spscase_term_taxonomies filter.
Yes. Since 1.3.0 the cache is invalidated by versioning its key, so scheduling or publishing a post refreshes the list immediately with any object cache backend.
Use the settings page to configure global defaults for appearance. You can also override settings on individual instances (widget, block, shortcode). For advanced customization, use the CSS classes documented below.
The REST API respects the same visibility settings as the other display methods. If you restrict visibility to logged-in users or editors, the API will also require authentication.
Yes! The plugin provides extensive hooks for developers. See the Developer Hooks section below for all available filters and actions with usage examples.
categories, tags, tax_<taxonomy>, authors and tax_mode, and post_type now accepts a comma-separated list. Terms and authors can be written as IDs or as slugs, and any of them accepts "all" to skip that filter.categories, tags, taxonomy, terms, authors and tax_mode, and post_type now accepts a comma-separated list or "all".spscase_filter_taxonomies, spscase_term_taxonomies, spscase_terms_limit, spscase_authors_limit and spscase_author_options filters.spscase_post_types filter now applies to every surface (settings, widget, block, shortcode and REST), not just to the settings dropdown.[scheduled-posts-showcase] now inherits what is configured in Appearance > Scheduled Posts, like the widget and the block already did, including the accent color.relative value documented for the spscase_date_format filter broke the output. It now renders "in 3 days" and keeps the absolute date in the title attribute of the time element.