Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WP 6.6: move from Post Editor to Site Editor versions of Utilities #37713

Closed
Tracked by #36721 ...
jeherve opened this issue Jun 5, 2024 · 1 comment · Fixed by #42652
Closed
Tracked by #36721 ...

WP 6.6: move from Post Editor to Site Editor versions of Utilities #37713

jeherve opened this issue Jun 5, 2024 · 1 comment · Fixed by #42652
Assignees
Labels
[Focus] Blocks Issues related to the block editor, aka Gutenberg, and its extensions developed in Jetpack [Focus] FSE Issues related to the site editor / Full Site Editing / FSE feature in Gutenberg [Pri] Normal [Type] Janitorial

Comments

@jeherve
Copy link
Member

jeherve commented Jun 5, 2024

WordPress 6.6 will start moving multiple utilities from @wordpress/edit-post to @wordpress/editor:

  • PluginSidebar
  • PluginPostStatusInfo
  • PluginMoreMenuItem
  • PluginSidebarMoreMenuItem
  • PluginDocumentSettingsPanel
  • PluginBlockSettingsMenuItem
  • PluginPostPublishPanel
  • PluginPrePublishPanel

We use some of those utilities in Jetpack plugins, we'll consequently start loading them from @wordpress/editor on sites that run WordPress 6.6, to avoid deprecation notices.

We should still support WordPress 6.5 for now though; only when WP 6.6 becomes the required version of WordPress in Jetpack plugins will we be able to fully remove backwards-compatibility code.


@jeherve jeherve added [Type] Janitorial [Focus] Blocks Issues related to the block editor, aka Gutenberg, and its extensions developed in Jetpack [Focus] FSE Issues related to the site editor / Full Site Editing / FSE feature in Gutenberg [Pri] Normal labels Jun 5, 2024
jeherve added a commit that referenced this issue Jun 12, 2024
This is related to the changes mentioned in #37713.

Starting in WP 6.6, we need to explicitely ensure that editor plugins that can only be used in the post editor are only loaded there.

- Epic: #36721
- Internal reference: p1718201200111879-slack-C03EL5U0PS6
jeherve added a commit that referenced this issue Jun 25, 2024
@coder-karen coder-karen self-assigned this Mar 13, 2025
@manzoorwanijk
Copy link
Member

manzoorwanijk commented Mar 21, 2025

Since WP 6.6 is now the required version for both Jetpack and Social following #40146, I have fixed the warnings for publicize-components in #42634

Requires at least: 6.6

Requires at least: 6.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Focus] Blocks Issues related to the block editor, aka Gutenberg, and its extensions developed in Jetpack [Focus] FSE Issues related to the site editor / Full Site Editing / FSE feature in Gutenberg [Pri] Normal [Type] Janitorial
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants