Make WordPress Core

Opened 4 weeks ago

Last modified 30 hours ago

#65286 new defect (bug)

major publishing action buttons are crowded in the Publish settings

Reported by: rlucian's profile rlucian Owned by:
Milestone: 7.0.1 Priority: normal
Severity: normal Version: 7.0
Component: Editor Keywords: has-patch
Focuses: administration Cc:

Description (last modified by desrosj)

Hi there,

On new WP 7 i have problems on publish section (right panel) because the new icons are too big and are not displayed correctly if WP Rocket plugin is active. I attach how it looks on WP 6.9.4 (are displayed OK) and on WP 7.0 (i use latest php 8.4). Hope you will fix the problem.

Attachments (7)

wp7-vs-wp6.zip (30.7 KB) - added by rlucian 4 weeks ago.
how the icons show on wp 7 and wp 6.9.4
wp-6.png (13.6 KB) - added by sabernhardt 4 weeks ago.
Publish meta box with Clear cache button above Move to Trash link in WordPress 6.9.4
wp-7.png (19.5 KB) - added by sabernhardt 4 weeks ago.
Move to Trash link is crowded between Clear Cache button and Publish link in WordPress 7.0
Screenshot 2026-05-21 at 09.52.10.png (17.3 KB) - added by cogdesign 4 weeks ago.
flex-wrap: wrap; to publish block
65286.diff (371 bytes) - added by abhishekfdd 3 weeks ago.
Screenshot 2026-05-27 111056.png (10.8 KB) - added by davidbaumwald 3 weeks ago.
Issue presenting in CPT without Classic Editor plugin
tic-tac-toe.php (1.7 KB) - added by jorbin 3 weeks ago.
Barebones plugin to show issue on a CPT

Download all attachments as: .zip

Change History (32)

@rlucian
4 weeks ago

how the icons show on wp 7 and wp 6.9.4

@sabernhardt
4 weeks ago

Publish meta box with Clear cache button above Move to Trash link in WordPress 6.9.4

@sabernhardt
4 weeks ago

Move to Trash link is crowded between Clear Cache button and Publish link in WordPress 7.0

#1 @sabernhardt
4 weeks ago

  • Component changed from Query to Editor
  • Focuses administration added
  • Milestone changed from Awaiting Review to 7.0.1
  • Summary changed from icons are to big into the publish settings to major publishing action buttons are crowded in the Publish settings

[61645] switched the #major-publishing-actions container to flex display with space-between.

Could you report this to WP Rocket in case they want to fix the issue in the plugin?

#2 @rlucian
4 weeks ago

Hi,

Thank you for your response. I will report this to WP Rocket too, but i'm doubt they will resolve it because i use an old verssion 3.8.8.

This ticket was mentioned in Slack in #core by wildworks. View the logs.


4 weeks ago

#4 @cogdesign
4 weeks ago

#major-publishing-actions {

padding: 10px;
clear: both;
border-top: 1px solid #dcdcde;
background: #f6f7f7;
display: flex;
align-items: center;
justify-content: space-between;
flex-wrap: wrap; <-- THIS NEEDS ADDING

}

@cogdesign
4 weeks ago

flex-wrap: wrap; to publish block

#5 @threadi
4 weeks ago

By the way, this also happens with Yoast Duplicate Post, in case anyone needs a free plugin to test a patch for this.

@abhishekfdd
3 weeks ago

#6 @abhishekfdd
3 weeks ago

  • Keywords has-patch added; needs-patch removed

Attaching a patch with the one-line fix suggested by @cogdesign in comment:4.

Root cause: [61645] converted #major-publishing-actions from float-based
layout to display: flex with justify-content: space-between. The container
is designed around two slots (Move to Trash on the left, Publish/Update on
the right), so any plugin that injects a third item via
post_submitbox_misc_actions or post_submitbox_start gets squeezed into
the middle.

The old float layout wrapped naturally when content overflowed, so this is
a layout regression in 7.0 rather than a plugin bug. Adding flex-wrap: wrap
restores wrap-on-overflow behavior while keeping the new flex alignment for
the default two-button case.

Verified the reproduction with both WP Rocket (per the report) and Yoast
Duplicate Post (per @threadi in comment:5). With the patch applied, the
injected button drops to its own line as it did in 6.9.4, and the default
no-plugin layout is unchanged.

Patch only touches the one rule — keeping the diff minimal for 7.0.1
backport. Happy to follow up with a small row-gap for vertical spacing
between wrapped rows in a separate ticket if that's preferred.

This ticket was mentioned in PR #11964 on WordPress/wordpress-develop by @abhishekfdd.


3 weeks ago
#7

Convert #major-publishing-actions to flex-wrap so third-party buttons injected via post_submitbox_misc_actions or post_submitbox_start fall to a new line instead of crowding the Move to Trash / Publish row.

Regression from [61645], which switched the container from floats to flex with space-between. Verified with WP Rocket and Yoast Duplicate Post.

Fixes #65286.

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

## Testing instructions

  1. Install and activate WP Rocket (or Yoast Duplicate Post — free).
  2. Edit any post.
  3. Observe in the Publish meta box: "Move to Trash" is crowded between the plugin-injected button and Publish/Update.
  4. Apply this patch.
  5. Reload the editor — the injected button now wraps to its own line and "Move to Trash" / Publish are spaced cleanly. Default no-plugin layout is unchanged.

#8 @darshitrajyaguru97
3 weeks ago

Test Report

Environment

  • WordPress: Latest trunk
  • Browser: Chrome
  • OS: Windows 10
  • Plugin tested:
    • WP Rocket
    • Yoast Duplicate Post (free)

Steps to Reproduce

  1. Install and activate WP Rocket (or Yoast Duplicate Post).
  2. Edit any existing post.
  3. Observe the Publish meta box layout:
    • "Move to Trash" appears crowded between the plugin-injected button and Publish/Update button.
  4. Apply the proposed patch.
  5. Reload the post editor.

Results

  • Before patch:

The plugin-injected button caused layout crowding inside the Publish meta box.
"Move to Trash" appeared squeezed between the injected button and Publish/Update button.

  • After patch:

The injected plugin button wraps onto its own line correctly.
"Move to Trash" and Publish/Update buttons now have proper spacing.
Default editor layout without plugins remains unchanged.

Conclusion

Patch tested successfully and works as expected.

#9 follow-up: @rlucian
3 weeks ago

I confirm too the patch is working but i see a new one on users -> profile. There i see two AI Functions texts which are not display correctly.

https://i.postimg.cc/qBZgGCfy/users-edit-user-profile.png

Last edited 3 weeks ago by rlucian (previous) (diff)

#10 @abhishekfdd
3 weeks ago

Thanks @darshitrajyaguru97 for the test report, and thanks @rlucian for
confirming the patch works for the original Publish meta box issue.

Regarding the "AI Functions" labels on the Users → Profile screen — that
looks unrelated to this ticket. The patch here only modifies
#major-publishing-actions, which is scoped to the post edit screen's
Publish meta box and doesn't affect the profile page.

The duplicate label appears to come from a third-party plugin (the
"Funcționalități AI" / "Revocă consimțământul" strings aren't from core).
Could you share which plugin is registering that field? It may be a
plugin-side issue, or — if it reproduces with no plugins active — worth
opening as a separate ticket so it can be triaged on its own merits.

Keeping this ticket focused on the Publish meta box fix so it stays
scoped for the 7.0.1 milestone.

#11 @sabernhardt
3 weeks ago

#65351 was marked as a duplicate.

#12 in reply to: ↑ 9 @deppierraz
3 weeks ago

Replying to rlucian:

I confirm too the patch is working but i see a new one on users -> profile. There i see two AI Functions texts which are not display correctly.

https://i.postimg.cc/qBZgGCfy/users-edit-user-profile.png

It's Yoast SEO, I've filled a report here https://github.com/yoast/wordpress-seo/issues/23164

This ticket was mentioned in Slack in #core by swissspidy. View the logs.


3 weeks ago

#14 @ocean90
3 weeks ago

#65354 was marked as a duplicate.

#15 @desrosj
3 weeks ago

  • Description modified (diff)

While this should be fixed here in Core, I think that a hotfix release can be pushed out to the Classic Editor plugin. Since this issue only presents when using that plugin (ignoring the user edit screen issue for now as that's unrelated), I think that makes the most sense until 7.0.1 can fix the issue in Core.

I've created a pull request for this.

@deppierraz @abhishekfdd @rlucian could you all give that a test?

@davidbaumwald
3 weeks ago

Issue presenting in CPT without Classic Editor plugin

#16 @davidbaumwald
3 weeks ago

Just wanted to note that as @jorbin suggested in Slack, this affects CPTs as well, even without the Classic Editor plugin installed/active. Confirmed this myself on my personal site.

This ticket was mentioned in Slack in #core by jorbin. View the logs.


3 weeks ago

@jorbin
3 weeks ago

Barebones plugin to show issue on a CPT

#19 @davidbaumwald
3 weeks ago

#65362 was marked as a duplicate.

This ticket was mentioned in Slack in #hosting by chaion07. View the logs.


2 weeks ago

This ticket was mentioned in Slack in #core by amykamala. View the logs.


2 weeks ago

This ticket was mentioned in Slack in #hosting by amykamala. View the logs.


2 weeks ago

This ticket was mentioned in Slack in #core-test by nikunj8866. View the logs.


13 days ago

#24 @sabernhardt
6 days ago

#65449 was marked as a duplicate.

#25 @siliconforks
30 hours ago

#65472 was marked as a duplicate.

Note: See TracTickets for help on using tickets.