WordPress 7.1 compatibility validation and Tested up to update
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 5
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Goal
Validate Perform against WordPress 7.1 before the scheduled 19 August 2026 release, then update the stable-tag readme only after compatibility evidence is complete.
Required work
- Test the packaged plugin on the latest WordPress 7.1 release candidate (and the supported PHP/browser matrix used by this repository).
- Run Plugin Check against the packaged plugin and record actionable findings.
- Review the applicable WordPress 7.1 changes: iframed post editor, client-side media processing, @wordpress/components changes, persistent editor toolbar, SVG Icon API, jQuery UI 1.14.2, and Abilities API changes. Mark non-applicable surfaces explicitly with evidence.
- Focus for this plugin: performance/admin dashboards, editor-facing assets, media processing hooks, and any Abilities API integration.
- Fix compatibility blockers in this release train; keep unrelated feature work out of scope.
- After proof passes, update the stable-tag
readme.txtline toTested up to: 7.1, refresh the changelog/release notes, and verify the packaged artifact contains the updated metadata.
Acceptance criteria
- WordPress 7.1 RC test site and relevant editor/admin workflows pass without new regressions.
- Plugin Check output is attached, with no unresolved release-blocking finding.
- Automated tests, lint/static checks, and package validation pass.
- The stable-tag readme update is made only after the above evidence exists.
- This issue is included in the milestone containing it and called out in the next minor release notes.
References
- WordPress 7.1 Field Guide: https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/
- Iframed editor changes: https://make.wordpress.org/core/2026/08/03/iframed-editor-changes-in-wordpress-7-1/
- Client-side media processing: https://make.wordpress.org/core/2026/07/22/client-side-media-processing-in-wordpress-7-1/
- Editor components: https://make.wordpress.org/core/2026/07/23/editor-components-updates-in-wordpress-7-1/
- Persistent toolbar: https://make.wordpress.org/core/2026/07/13/consistent-navigation-in-wordpress-7-1-with-persistent-toolbar/
- SVG Icon API: https://make.wordpress.org/core/2026/07/24/registering-and-rendering-svg-icons-in-wordpress-7-1/
- jQuery UI 1.14.2: https://make.wordpress.org/core/2026/07/29/jquery-ui-updated-to-1-14-2-in-wordpress-7-1/
- Abilities API: https://make.wordpress.org/core/2026/07/31/abilities-api-improvements-in-wordpress-7-1/
- Plugin Check: https://wordpress.org/plugins/plugin-check/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the packaged plugin on a WordPress 7.1 release-candidate test site, covering the supported PHP/browser matrix and the listed editor, media, admin, and Abilities API surfaces. Run Plugin Check and the repository's automated tests, lint, static checks, and package validation; record evidence for applicable and non-applicable changes. Done means release blockers are resolved, the artifact is verified, and stable-tag readme.txt and release notes are updated only after the checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- documentation, performance, release, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100