- New: Display changelogs from any plugin hosted on WordPress.org
- New: Filter for âchangelog-serviceâ post type arguments
- Change: Post type rewrite slug changed to âchangelog-detailsâ to better avoid permalink collisions
- Fix: Processing EDD changelogs with HTML structure
đ New: Display Changelogs From Any Plugin Hosted on WordPress.org
This feature allows you to pull a changelog directly from WordPress.org, so you don’t have to create a new changelog on your site. Using either method below, the changelog will be fetched from WordPress.org and cached for 24 hours.
Block Editor/Gutenberg
- Add the Changelog block to your page or post
- From the Changelog Source dropdown, select WordPress.org Plugin
- Enter the plugin slug in the text field (e.g., “akismet,” “jetpack,” “woocommerce”)
Shortcode
- Add a shortcode solution (e.g., “block,” “widget,” etc.) to your page or post
- Add a shortcode similar to:
[changelog_service plugin_slug="akismet"]đ New: Filter for âchangelog-serviceâ Post Type Arguments
This new filter allows you to change the arguments used to set up the post type.
$args = apply_filters( 'caas_post_type_args', $args );
register_post_type( self::POST_TYPE, $args );⥠Change: Post Type Rewrite Slug Changed to âChangelog-Detailsâ to Better Avoid Permalink Collisions
Changelogs are set up as a post type with a public URL, and the default URL was:
url.com/changelog/[slug]This caused a URL conflict because users wanted to create a page with a “changelog” slug (url.com/changelog) and then insert the shortcode/block on this page.
The new default URL is:
url.com/changelog-service/[slug]