Conversation
The Extended Post Status dropdown was not appearing in the block editor because SelectControl and PluginPostStatusInfo were used but never imported, causing the registerPlugin call to fail silently. Also refactored webpack.config.js to use separate configurations for each entry point: custom-status-block now uses default wp-scripts externalization since it runs in the block editor where @WordPress packages are available as globals, while calendar-react continues to bundle them for use outside the editor context. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
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.
Summary
The "Extended Post Status" dropdown was not appearing in the block editor sidebar when editing posts. This panel allows users to select custom statuses (Pitch, Assigned, In Progress, etc.) instead of the core WordPress statuses.
Root cause:
SelectControlandPluginPostStatusInfowere used incustom-status-block.jsbut never imported, causing theregisterPlugin()call to fail silently.Additional fix: Refactored
webpack.config.jsto use separate configurations:custom-status-block: Uses default wp-scripts externalization (runs in block editor where @WordPress packages are globals)calendar-react: Bundles @WordPress packages (runs outside block editor context where globals aren't available)Test plan
🤖 Generated with Claude Code