Make WordPress Core

Opened 15 months ago

Closed 15 months ago

Last modified 15 months ago

#45422 closed defect (bug) (duplicate)

Admin alerts conflict with Gutenberg editor in WordPress 5 RC1

Reported by: foomagoo Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Editor Keywords:
Focuses: Cc:


Alerts added with the admin_notices hook no longer work as they should with the new Gutenberg editor in WordPress 5 RC1-43944. In my plugins I add an admin alert to the page by using the admin_notices action hook. These notices should appear above the content of the post edit screen. When the admin notices are printed to the screen with the new version of wordpress they are set to a fixed position with the core css and are stuck over top of the post editor. Notices from other plugins disappear completely. You can test this by installing Plugin Organizer. Selective plugin loading and selective admin plugin loading must both be enabled before the debug message will appear on top of the post editor.

Change History (4)

#1 @desrosj
15 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to duplicate
  • Status changed from new to closed

Thanks for the ticket, @foomagoo!

This is already being tracked in #45405 on Trac, and GB-12301/GB-12243.

Please add details in these locations to keep the conversation in one place.

It's worth noting that only admin notices that use the Core notice classes (.notice, .notice-error, .notice-warning, .notice-info) are currently being fed to the Notice API in the new editor. If you are using other custom styling, expressing that on the tickets listed above would be very helpful!

#2 @foomagoo
15 months ago

Sorry about that. I searched for similar tickets but couldn't find any. I'm using the notice notice-warning and notice notice-error classes.

#3 @desrosj
15 months ago

No problem at all, @foomagoo! I would follow up on GitHub that your notices are not being consumed for some reason, then.

#4 @desrosj
15 months ago

  • Version 5.0 deleted
Note: See TracTickets for help on using tickets.