Skip to content

Conversation

@GaryJones
Copy link
Contributor

@GaryJones GaryJones commented Jan 12, 2026

Summary

Release 0.10.3 with bug fixes and improvements.

Added

  • WordPress Playground blueprint for live preview (#885)

Fixed

  • Prevent Edit Flow nonce checks from killing unrelated forms (#883)
  • Add missing imports for Extended Post Status block editor panel (#884)

Documentation

  • Move Development section from README to CONTRIBUTING (#880)

Maintenance

  • Optimise CI workflows with path filters and split tests (#881)
  • Add integration test for revision nonce handling (#879)

GaryJones and others added 17 commits January 7, 2026 16:33
Jest unit tests don't need wp-env, so separating them provides faster
feedback for pure JS changes. E2E tests still require the full
WordPress environment with Playwright.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
The notifications module was incorrectly checking the generic `_wpnonce` field against Edit Flow's expected action when posts were saved. This caused contact forms and other plugins that triggered post status transitions to fail, as Edit Flow would call `wp_die()` when their unrelated nonces didn't verify against Edit Flow's action.

The fix ensures Edit Flow only processes its own form submissions by checking for the presence of `ef-save_followers` before performing any nonce verification. When Edit Flow's form is submitted, it now verifies against its own dedicated `ef_notifications_nonce` field with the `save_user_usergroups` action, rather than checking the generic `_wpnonce` that other forms might use.

Additionally, the AJAX handler `handle_user_post_subscription()` had a security vulnerability where requests without any nonce would pass through due to faulty logic (`!empty && !verify` instead of `empty || !verify`). This has been corrected to properly require a valid nonce.

The changes also improve error handling by returning early instead of calling `wp_die()` in the `save_post_subscriptions()` hook. This prevents Edit Flow from terminating requests during the `transition_post_status` action, which fires for all post changes regardless of context.

Fixes #882

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
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>
Enable the WordPress.org "Live Preview" feature by adding a Playground blueprint configuration. This allows potential users to explore Edit Flow's features interactively before installation.

The blueprint demonstrates the plugin's editorial workflow capabilities by creating a realistic scenario with multiple users (editor and writer), sample posts across different custom statuses (pitch, assigned, in-progress, pending, draft, scheduled), and editorial comments showing team collaboration. Users land directly on the Calendar view to immediately showcase the editorial calendar feature.

Inspired by Co-Authors Plus PR #1184.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@GaryJones GaryJones requested a review from a team as a code owner January 12, 2026 15:47
@GaryJones GaryJones added the type: release Release-related tasks label Jan 12, 2026
@GaryJones GaryJones self-assigned this Jan 12, 2026
@GaryJones GaryJones added this to the 0.10.3 milestone Jan 12, 2026
@GaryJones GaryJones merged commit 410f6f9 into main Jan 12, 2026
12 checks passed
@GaryJones GaryJones deleted the release/0.10.3 branch January 12, 2026 15:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: release Release-related tasks

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants