Requires WordPress 5.0 Tested up to WordPress 6.5
- Make sure to register statuses after locale has been switched (See #89)
- Hide visibility panel in WordPress 6.5 (See #91)
@bonny @rodrigo-arias
Requires WordPress 5.0 Tested up to WordPress 6.4
- Do not use
WP_DEBUG
to check whether testing script needs to be loaded (See #87)
Requires WordPress 5.0 Tested up to WordPress 6.3
- Avoid the "Auto Draft" initial post title in Block Editor
- Make sure lodash is loaded into the Block Editor.
- Prevent a PHP 8.2 deprecated notices.
- Fixes some typos about the "attributes" word.
@szepeviktor @claytoncollie @shawfactor
Requires WordPress 5.0 Tested up to WordPress 6.1
- Prevent a PHP 8.2 deprecated notice.
- Avoid a possible error notice (that may be generated by third party plugins).
- Use a timezoned date to check the future status.
- Ensure the REST API status hijack is only applied in the admin.
- Update ParcelJS to 2.0.
@BronsonQuick @elvishp2006 @bonny @maennchen
Requires WordPress 5.0 Tested up to WordPress 5.9
- Stop using WP i18n Grunt task and @wordpress/babel-plugin-makepot to generate pot/json files.
- Use
wp.date.isInTheFuture()
to check whether a post type is scheduled or not. - Make sure the link to browse revisions is added into the Classic Editor.
@pdobrescu
Requires WordPress 5.0 Tested up to WordPress 5.8.0
- For WordPress >= 5.8, stop using the deprecated filter
block_editor_preload_paths
in favor ofblock_editor_rest_api_preload_paths
.
@rodrigo-arias
Requires WordPress 5.0 Tested up to WordPress 5.7.0
- Makes the WP_Statuses_Core_Status::_builtin property public, so it is accessible by
is_post_status_viewable()
.
@andronocean
Requires WordPress 5.0 Tested up to WordPress 5.5.1
- Make sure the plugin can be used with the Classic Editor plugin when WP is >= 5.5 or WP is < 5.5.
@andrefredette
Requires WordPress 5.0 Tested up to WordPress 5.4.1
- Make sure trashing a post from the Block Editor is redirecting the user on the edit screen of the post type.
- Make sure Post types
template
andtemplate_lock
properties are taken in account and that the blocks set in the template are inserted into the Block Editor.
@leorospo
Requires WordPress 5.0
- Italian translation.
@leorospo
Requires WordPress 5.0
- WP Statuses is now ready to manage your custom statuses within the WordPress Block Editor 🙌
@rowatt
Requires WordPress 4.7
- Fix PHP warnings for scheduled posts.
@rowatt, @lajala
Requires WordPress 4.7
- Adds a Composer config file.
@AdamQuadmon
Requires WordPress 4.7
- Adds the missing CHANGELOG to repository.
- Spanish translation.
- Use the Git Archive npm module instead of the compress one.
@delmicio
Requires WordPress 4.7
- Adds the missing GNU/GPL2 license to repository.
- Adds a `Github Plugin URI header tag for easier upgrades using the Github Updater plugin or the Entrepôt plugin.
- Adds a plugin icon to be used by the Entrepôt plugin.
Requires WordPress 4.7
- Avoid confusions between taxonomy terms and statuses for the custom example.
- Make sure the Attachment post type is not concerned by custom statuses.
- German translation.
- Introduce a filter to remove the custom post statuses support from custom post types.
@mediastuttgart @toshotosho
Requires WordPress 4.7
- Avoid confusions between taxonomy terms and statuses for the custom example.
- Introduce more customizable labels for the Metabox strings.
- Make the Publishing Metabox JavaSscript less dependant of WordPress & ready for custom labels.
@GaryJones
Requires WordPress 4.7
- Make sure custom statuses cannot be sticked to front.
- Add a property to support custom statuses integration within Press This.
Requires WordPress 4.7
- Improve the WordPress Post statuses API by allowing custom Post statuses.