wp-admin » WordPress 7.2 Editor Options Menu: Plugin Items Move to Panels

WordPress 7.2 Editor Options Menu: Plugin Items Move to Panels

WordPress 7.2 rebuilds the Options menu (the ⋮ button in the top right of the post and site editor) and the View menu on top of the new Menu component from @wordpress/ui. For most people nothing breaks, but one thing moves: menu items added by plugins no longer sit in their own “Plugins” group. They now live in a Panels submenu.

That affects three groups of people. Editors who suddenly cannot find the menu entry of their SEO or AI plugin. Developers who styled the old menu with CSS. And plugin authors who pass the undocumented as prop or have end-to-end tests that click through the old menu.

As of 2026-11-15, 7.2 is still in beta (Beta 5 shipped on November 10) and the final release is scheduled for December 8, 2026, so this is the right week to check your plugins and admin tweaks before the final release.


Open a post, click the ⋮ Options button, then open Panels. Items registered with PluginMoreMenuItem or PluginSidebarMoreMenuItem show up there, with the same label and icon they had before.

Nothing is lost and nothing needs to be reinstalled. The item is one click deeper, that’s all. If your team writes internal how-tos with screenshots of the old menu (“click the three dots, then Yoast”), update them now so nobody files a “plugin is broken” ticket after the update.


Never test a beta on the live site. Clone the site to staging, back up its database, then switch the copy to the beta channel. The simplest way is the official WordPress Beta Tester plugin:

wp db export before-7-2-beta.sql
wp plugin install wordpress-beta-tester --activate

Then go to Tools > Beta Testing, switch to the Bleeding edge channel and pick the beta/RC stream, and update from Dashboard > Updates. The plugin page has the details. Run wp core version afterwards; it should print a 7.2 beta or RC version, not 7.1.x.

The three components that add items to these menus are PluginMoreMenuItem, PluginSidebarMoreMenuItem and PluginPreviewMenuItem. Their names survive minification because plugins read them from the global wp.editor object, so a plain grep finds them even in built files:

cd /path/to/wordpress/wp-content
grep -rlE "Plugin(More|SidebarMore|Preview)MenuItem" plugins themes mu-plugins --include=*.js 2>/dev/null | grep -v node_modules

You get a list of JavaScript files. The folder name tells you which plugin or theme it belongs to. No output means nothing on the site adds items to these menus, and you can skip to the CSS check below.

Next, open the editor on staging with the browser console open (F12). If a plugin still uses the as prop, WordPress 7.2 logs this deprecation warning:

The `as` prop of wp.editor.PluginMoreMenuItem is deprecated since version 7.2. Note: The menu renders the item itself. The prop is ignored.

The menu item still appears, but whatever custom component the plugin passed through as is ignored. If that component did more than render a button (a custom modal trigger, a tracking wrapper), that extra behavior is gone. Report it to the plugin author with the warning text.


If you maintain the plugin, the fix is small. The dev note on make.wordpress.org says the supported props are icon, onClick, href and disabled, with the label passed as children. PluginSidebarMoreMenuItem also takes target.

Code like this, where a custom button component is injected:

<PluginMoreMenuItem as={ MyFancyButton } icon={ external } onClick={ openMyTool }>
	Open my tool
</PluginMoreMenuItem>

becomes this, which is the example from the dev note:

<PluginMoreMenuItem icon={ external } onClick={ openMyTool }>
	Open my tool
</PluginMoreMenuItem>

Move whatever logic lived in MyFancyButton into the onClick handler. If it opened a sidebar, use PluginSidebarMoreMenuItem with target instead of wiring that up yourself. The menu now renders the item itself, so there is no supported way to swap in your own markup.

See also  WordPress 7.1 Client-Side Image Processing: How to Disable It

💡 Code that uses ActionItem from @wordpress/interface directly can still pass as, but the dev note says your component must then forward its props and ref to the DOM element.

The new menu uses different markup. Styles that target class names from @wordpress/components, such as .components-menu-item__button, no longer match inside these two menus. Search your admin CSS for them:

grep -rn "components-menu-item" wp-content/themes wp-content/plugins wp-content/mu-plugins --include=*.css --include=*.scss --include=*.php 2>/dev/null | grep -v node_modules

Not every hit is a problem, because other editor menus may still use those classes. Test each rule on staging: open the Options and View menus and see whether your styling (hidden items, brand colors, bigger tap targets) still applies.

If you hid a menu item with CSS, I would not chase the new class names. Internal markup can change again in the next release. Remove the item at the source instead, by not registering it, or ask the plugin author for a setting. I wrote about the same kind of breakage for admin menu icons in WordPress 7.2 SVG admin icons.

Playwright tests that clicked a CSS selector or looked for a “Plugins” group will fail on 7.2. The dev note recommends selecting items by role and accessible name, opening Panels first:

await page.getByRole( 'menuitem', { name: 'Panels', exact: true } ).click();
await page.getByRole( 'menuitemcheckbox', { name: 'Open my tool', exact: true } ).click();

Role-based selectors are also more stable in general, because they follow what the user sees rather than generated class names.


The block editor is slowly replacing old @wordpress/components pieces with new, more accessible ones from @wordpress/ui. Each swap keeps the public API (the Plugin*MenuItem components still work) but changes the HTML underneath. Anything that depends on that HTML, like CSS overrides, DOM scripts and brittle tests, breaks quietly.

The way to stay ahead is boring but it works: run staging on the beta for a week before every major release, and keep editor customizations on documented APIs. If the editor misbehaves in other ways after an update, my posts on a blank Site Editor and changing the editor width cover other common tweaks.

TL;DR: In WordPress 7.2, plugin entries in the editor’s ⋮ Options menu move into a Panels submenu. Users just need to look one level deeper. Developers should remove the ignored as prop, stop styling .components-menu-item__button in those menus, and switch tests to role-based selectors before 7.2 goes final.

Was this post helpful?

Leave a Comment

I enjoy constructive responses and professional comments to my posts, and invite anyone to comment or link to my site.

Recommended