Skip to content

Latest commit

 

History

History
309 lines (168 loc) · 4.92 KB

CHANGELOG.md

File metadata and controls

309 lines (168 loc) · 4.92 KB
Raw

Change Log

2.1.9

Requires WordPress 5.0 Tested up to WordPress 6.6

Bug Fixes

  • Hide visibility panel in WordPress 6.6 (See #94)

Props

@shawfactor

2.1.8

Requires WordPress 5.0 Tested up to WordPress 6.5

Bug Fixes

  • Make sure to register statuses after locale has been switched (See #89)
  • Hide visibility panel in WordPress 6.5 (See #91)

Props

@bonny @rodrigo-arias

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)

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

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

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

@pdobrescu

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 of block_editor_rest_api_preload_paths.

Props

@rodrigo-arias

2.1.2

Requires WordPress 5.0 Tested up to WordPress 5.7.0

Bug Fixes

  • Makes the WP_Statuses_Core_Status::_builtin property public, so it is accessible by is_post_status_viewable().

Props

@andronocean

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

@andrefredette

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.

Props

@leorospo

2.0.1

Requires WordPress 5.0

Features

  • Italian translation.

Props

@leorospo

2.0.0

Requires WordPress 5.0

Features

  • WP Statuses is now ready to manage your custom statuses within the WordPress Block Editor 🙌

Props

@rowatt

1.2.5

Requires WordPress 4.7

Bug Fixes

  • Fix PHP warnings for scheduled posts.

Props

@rowatt, @lajala

1.2.4

Requires WordPress 4.7

Features

  • Adds a Composer config file.

Props

@AdamQuadmon

1.2.3

Requires WordPress 4.7

Bug fixes

  • Adds the missing CHANGELOG to repository.

Features

  • Spanish translation.
  • Use the Git Archive npm module instead of the compress one.

Props

@delmicio

1.2.2

Requires WordPress 4.7

Bug fixes

  • Adds the missing GNU/GPL2 license to repository.

Features

  • 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.

1.2.1

Requires WordPress 4.7

Bug fixes

  • Avoid confusions between taxonomy terms and statuses for the custom example.
  • Make sure the Attachment post type is not concerned by custom statuses.

Features

  • German translation.
  • Introduce a filter to remove the custom post statuses support from custom post types.

Props

@mediastuttgart @toshotosho

1.2.0

Requires WordPress 4.7

Bug fixes

  • Avoid confusions between taxonomy terms and statuses for the custom example.

Features

  • Introduce more customizable labels for the Metabox strings.
  • Make the Publishing Metabox JavaSscript less dependant of WordPress & ready for custom labels.

Props

@GaryJones

1.1.0

Requires WordPress 4.7

Bug fixes

  • Make sure custom statuses cannot be sticked to front.

Features

  • Add a property to support custom statuses integration within Press This.

1.0.0

Requires WordPress 4.7

Features

  • Improve the WordPress Post statuses API by allowing custom Post statuses.