| 开发者 | jumplinks |
|---|---|
| 更新时间 | 2026年5月19日 18:59 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/jumplinks-editorial-workflow directory, or install the plugin through the WordPress plugins screen.Assign a reviewer, submit for review, collect inline comments, request changes or approve, and then publish when the content is ready.
Flow is designed for Gutenberg, Classic Editor, Elementor, and Bricks Builder publishing workflows.
Yes. Flow supports Elementor-based publishing workflows and review collaboration.
Yes. Flow includes support for Classic Editor workflows alongside Gutenberg.
Yes. Flow adds a Review button to the Bricks toolbar (next to Save) that opens a Bricks-themed review drawer with reviewer assignment, status, and approve / request changes actions. When mandatory review is enabled, the Publish button is automatically disabled until the post is approved.
Flow ships with native integrations for Gutenberg, Classic Editor, Elementor, and Bricks Builder. If you work in a different editor, you can still use Flow — just open the post in Gutenberg or Classic Editor (both included with WordPress) to request reviews, manage reviewers, and track status. Your existing editor stays untouched for the actual content work.
Yes. You can enable the review workflow for posts, pages, products, and custom post types from the settings screen.
Yes. Flow sends email notifications for key review lifecycle events, helping teams stay aligned on status changes.
Yes. Flow is compatible with WooCommerce-powered sites and content workflows.
Flow is ideal for content and editorial teams that need a simple review and approval workflow in WordPress without the overhead of enterprise-style configuration. It also works well for freelance developers and agencies who want a structured way to share in-progress work with clients for feedback and approval, without sending screenshots or asking clients to navigate the WordPress admin.
Yes. Add the client as a user with a reviewer-eligible role, assign them as the reviewer, and send them the review page link. They land on a focused page with the page or post preview, leave inline comments anchored to specific content, and approve or request changes — without ever needing to learn the WordPress editor.
*.l10n.php translation file now declares a direct-access guard, resolving a Plugin Checker warning.font-family: "<post title>" instead of the real font name.<a> (gallery markup) no longer collapse to their intrinsic size.<a><img></a> markup now opens the comment popover when clicked instead of being swallowed by the review-page link guard.onclick="window.open( '…', '_self' )" handlers (common in galleries) no longer navigate the review iframe out of the chrome — same _blank bypass as target="_blank" anchors..entry-content / .wp-block-post-content.assets/blueprints/blueprint.json so the WordPress.org plugin page can spin up a one-click demo of the review experience (logged in as a reviewer with sample image/video content to comment on).template_include (e.g. Kallyas builder, other site-builder themes), so the dedicated review page renders correctly regardless of the active theme.button / [type=button] selectors.languages/, plus Domain Path header, so translate.wordpress.org community translations are picked up automatically.react-jsx-runtime script handle that core only registers from 6.6 onwards, restoring the review page chrome and editor sidebars on older WP versions.