Skip to content

Media: Re-introduce client-side media processing feature#11324

Open
adamsilverstein wants to merge 1 commit intoWordPress:trunkfrom
adamsilverstein:reintroduce-client-side-media
Open

Media: Re-introduce client-side media processing feature#11324
adamsilverstein wants to merge 1 commit intoWordPress:trunkfrom
adamsilverstein:reintroduce-client-side-media

Conversation

@adamsilverstein
Copy link
Member

@adamsilverstein adamsilverstein commented Mar 20, 2026

Summary

  • Reverts the removal in [62081] now that WordPress 7.1 has forked
  • Restores all PHP functions, REST API endpoints, cross-origin isolation infrastructure, VIPS script module handling, build configuration, and associated tests
  • 14 files restored, ~1,625 lines

Test plan

  • CI passes (coding standards, PHPUnit, JS tests)
  • Verify client-side media processing functions are restored in wp-includes/media.php
  • Verify REST API endpoints for attachments are restored
  • Verify cross-origin isolation test suite passes
  • Verify VIPS script module registration is restored

Trac ticket: https://core.trac.wordpress.org/ticket/64919

Props adamsilverstein, jorbin.
See #64906.

@github-actions
Copy link

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 props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props adamsilverstein.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Reverts the removal in [62081] now that WordPress 7.1 has forked. Restores all PHP functions, REST API endpoints, cross-origin isolation infrastructure, VIPS script module handling, build configuration, and associated tests.

Props adamsilverstein, jorbin.
See #64906.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@github-actions
Copy link

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant