WordPress 7.2 editor menus: check the route to custom tools

Hands using a laptop keyboard beside a notebook on a wooden table.

A plugin panel can still exist after an editor update while the test that opens it fails. WordPress’s 11 November developer note describes changes to the Options and View menus planned for WordPress 7.2. Agencies maintaining custom editorial tools should check how staff reach those tools before the upgrade.

The change covers the post and site editors. Plugin entries move into a Panels submenu, and old menu class selectors need attention. The supported plugin menu components remain available; developers should review undocumented customisation rather than assume every extension needs rebuilding.

Start with the editor’s actual job

Choose an editorial task that depends on your plugin: opening a briefing panel, checking a publication setting or following a preview link. Write down the starting screen, the action and the expected result. Use a safe test environment containing representative content.

Ask an editor to follow the existing instructions. Record where the path differs from the documented process. A changed menu location may need a training update even when the underlying feature works correctly.

Check how tests find the item

The developer note recommends selecting menu entries by role and name. Tests must open Options, then Panels, before locating the plugin item. Inspect any automation that still depends on a class such as .components-menu-item__button.

Keep the expected outcome visible in the test record. Reaching a menu entry proves only that the route exists. Continue through the action and confirm that it opens the intended interface with the expected content. Include a disabled-state check if the tool has one.

Review custom menu rendering

WordPress says the undocumented as prop on its plugin menu components will be ignored with a deprecation warning in 7.2. Its advised fix is to remove that prop and use the documented properties. Importing a separate new menu item component isn’t the suggested migration.

Give the developer a list of the affected extensions and their owners. Don’t replace an unfamiliar component without checking what behaviour the original supplied. A custom link or permission condition deserves its own acceptance check, alongside the visual result.

Record a result someone else can repeat

For each check, retain the WordPress build, plugin version and user role. Add the route taken through the menus and the observed result. Remove personal content from screenshots before sharing them with a supplier.

Our guide to testing a WordPress bug fix explains how to turn a reproduction into useful feedback. Apply that discipline here: distinguish a broken feature from an outdated selector or help document.

Finish with a decision for each custom tool: ready for the tested build, needs a documented change, or still unverified. Treat this as preparation for 7.2; the developer note doesn’t establish that your production site has received the update.

Need expert WordPress support?

Whether it's custom development, performance issues, or ongoing maintenance—we've got you covered. Let's talk about keeping your WordPress site running at its best.