-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Media: Graduate client-side media processing from experimental #75112
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
base: trunk
Are you sure you want to change the base?
Conversation
…table Move the media processing module from lib/experimental/media/ to lib/media/ as part of graduating this feature from experimental status. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Remove the experiment toggle as this feature is now graduated to stable. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Remove the experiment check and always load the media processing module from its new stable location. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Replace experiment check with gutenberg_client_side_media_processing_enabled filter that defaults to true. This allows sites to disable the feature while keeping it enabled by default. Also rename the window global from __experimentalMediaProcessing to __clientSideMediaProcessing to reflect stable status. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add early return when client-side media processing is disabled via filter. Update docblocks and comments to reflect stable status. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Use the gutenberg_client_side_media_processing_enabled filter to determine whether to use the 6.9 compat REST controller for attachments. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Update all JavaScript references from __experimentalMediaProcessing to __clientSideMediaProcessing to reflect the stable status of this feature. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add documentation to test files and add new tests for the gutenberg_client_side_media_processing_enabled filter. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Consolidates the duplicated `gutenberg_client_side_media_processing_enabled` filter calls into a single helper function `gutenberg_is_client_side_media_processing_enabled()` in lib/load.php. This follows the same pattern as `gutenberg_is_experiment_enabled()` and reduces code duplication across three files. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
Size Change: +26 B (0%) Total Size: 3 MB
ℹ️ View Unchanged
|
Summary
lib/experimental/media/tolib/media/gutenberg_client_side_media_processing_enabledfilter (defaults totrue) allowing sites to disable the feature if neededwindow.__experimentalMediaProcessingtowindow.__clientSideMediaProcessingTest plan
add_filter( 'gutenberg_client_side_media_processing_enabled', '__return_false' );to a pluginCloses #75062
🤖 Generated with Claude Code