This repository has been archived by the owner on Nov 17, 2024. It is now read-only.
Releases: imath/wp-statuses
Releases · imath/wp-statuses
WP Statuses 2.1.9
Requires WordPress 5.0
Tested up to WordPress 6.6
What's Changed
- Hide visibility panel in WordPress 6.6 (See #94)
Full Changelog: 2.1.8...2.1.9
WP Statuses 2.1.8
Requires WordPress 5.0
Tested up to WordPress 6.5
What's Changed
- Run wp_statuses_register function on change_locale hook by @bonny in #90
- Hide visibility panel in WordPress 6.5 by @rodrigo-arias in #92
New Contributors
Full Changelog: 2.1.7...2.1.8
WP Statuses 2.1.7
Requires WordPress 5.0
Tested up to WordPress 6.4
Bug Fixes
- Do not use
WP_DEBUG
to check whether testing script needs to be loaded (See #87)
Upgrade/Installation
- You can use the Entrepôt to automatically install or upgrade WP Statuses
- If you're doing the installation or upgrade manually, make sure the content of
wp-statuses.zip
is located within the/wp-content/plugins/
directory of your WordPress.
WP Statuses 2.1.6
Requires WordPress 5.0
Tested up to WordPress 6.3
Bug Fixes
- 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.
Props
@szepeviktor @claytoncollie @shawfactor
Upgrade/Installation
- You can use the Entrepôt to automatically install or upgrade WP Statuses
- If you're doing the installation or upgrade manually, make sure the content of
wp-statuses.zip
is located within the/wp-content/plugins/
directory of your WordPress.
WP Statuses 2.1.5
Requires WordPress 5.0
Tested up to WordPress 6.1
Bug Fixes
- 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.
Props
@BronsonQuick @elvishp2006 @bonny @maennchen
Upgrade/Installation
- You can use the Entrepôt to automatically install or upgrade WP Statuses
- If you're doing the installation or upgrade manually, make sure the content of
wp-statuses.zip
is located within the/wp-content/plugins/
directory of your WordPress.
WP Statuses 2.1.4
Requires WordPress 5.0
Tested up to WordPress 5.9
Bug Fixes
- 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.
Props
Upgrade/Installation
- You can use the Entrepôt to automatically install or upgrade WP Statuses
- If you're doing the installation or upgrade manually, make sure the content of
wp-statuses.zip
is located within the/wp-content/plugins/
directory of your WordPress.
WP Statuses 2.1.3
Requires WordPress 5.0
Tested up to WordPress 5.8.0
Bug Fixes
- For WordPress >= 5.8, stop using the deprecated filter
block_editor_preload_paths
in favor ofblock_editor_rest_api_preload_paths
.
Props
Upgrade/Installation
- You can use the Entrepôt to automatically install or upgrade WP Statuses
- If you're doing the installation or upgrade manually, make sure the content of
wp-statuses.zip
is located within the/wp-content/plugins/
directory of your WordPress.
WP Statuses 2.1.2
Requires WordPress 5.0
Tested up to WordPress 5.7
Bug Fixes
- Makes the WP_Statuses_Core_Status::_builtin property public, so it is accessible by
is_post_status_viewable()
.
Props
WP Statuses 2.1.1
Requires WordPress 5.0
Tested up to WordPress 5.5.1
Bug Fixes
- Make sure the plugin can be used with the Classic Editor plugin when WP is >= 5.5 or WP is < 5.5.
Props
WP Statuses 2.1.0
Requires WordPress 5.0
Tested up to WordPress 5.4.1
Bug Fixes
- 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 and template_lock properties are taken in account and that the blocks set in the template are inserted into the Block Editor.