Support » Requests and Feedback » Coherent strategy for admin notices

  • The display of Admin Notices in the backend is pretty simple as currently implemented. We have an action hook we can latch onto to spew output at the top of the page.

    This system is accessible to abuse and frequently abused.

    • Notices from a plugin can be littered onto every single page backend page of the site
    • Copious notice-litter creates notice blindness among users
    • There is not enforcement of formatting so abusive plugins and spew whatever obnoxious messaging formats the plugin author likes.

    As a developer, I would like to see a more coherent and structured admin-notice flow where…

    • Notices are registered to the core with simple $notice_type, $notice_text args (type being ‘error’, ‘info’, ‘success’, etc)
    • Notices are displayed uniformly by the core
    • Notices can be restricted to space (admin pages) where the plugin has authority (e.g. other plugins aren’t littering my plugin’s pages)

    Does this seem like something that other developers would like?

Viewing 3 replies - 1 through 3 (of 3 total)
  • I think you’re onto a good point, but if a plugin is showing too much noise in the admin area then just remove it and/or tell the plugin developer. It’s a difficult thing to try and manage because some plugins may show a notice everywhere which is important, and others might be using it just for spamming.



    Hmmm…. in my opinion it’s not good idea. There are many other way

    @danieltj – the advice to “just remove it” isn’t really feasible if you are joining a WordPress blog that where those plugins are deemed important enough to keep in spite of their bad behavior with notices. Honestly, I can’t think of an instance where one plugin has something so important to report that is should spew on another plugin’s backend pages.

    @krysia81 – feel free to elaborate.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Coherent strategy for admin notices’ is closed to new replies.