Broken: Update PluginDocumentSettingPanel to load from new location#32
Draft
Broken: Update PluginDocumentSettingPanel to load from new location#32
Conversation
Owner
Author
|
If I'm following correctly, this fails in older versions of WordPress because of the dependencies. Before Updating @wordpress/scriptsAfter Updating @wordpress/scripts
|
Update @wordpress/scripts from 22.5.0 to the latest, 28.4.0 This was accomplished by running npm install @wordpress/scripts@28.4.0 --force See #31
Change source for PluginDocumentSettingPanel from @wordpress/edit-post to @wordpress/editor To address the change introduced in WordPress 6.6 Resolves #31
salcode
force-pushed
the
chore/plugin-settings-panel-package-move-31
branch
from
35042a6 to
dede025
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR works for WordPress 6.6 but is not backwards
compatible with older versions of WordPress core (e.g. WordPress 6.5)
See #31