Title: PHP notices in post editor
Last modified: November 13, 2018

---

# PHP notices in post editor

 *  Resolved [Spiffy Plugins](https://wordpress.org/support/users/spiffyplugins/)
 * (@spiffyplugins)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/php-notices-in-post-editor/)
 * I am running WP 5.0-beta3-43891 with the Query Monitor plugin while updating 
   my plugins for block edits. I noticed that recently 2 PHP error notices are generated
   by core in the post editor:
 * “edit_form_after_title is deprecated since version 5.0.0! Use block_editor_meta_box_hidden_fields
   instead. This action is still supported in the classic editor, but is deprecated
   in the block editor.”
 * “edit_form_advanced is deprecated since version 5.0.0! Use block_editor_meta_box_hidden_fields
   instead. This action is still supported in the classic editor, but is deprecated
   in the block editor.”

Viewing 10 replies - 1 through 10 (of 10 total)

 *  [Jacob Peattie](https://wordpress.org/support/users/jakept/)
 * (@jakept)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/php-notices-in-post-editor/#post-10876088)
 * They notices seem pretty clear to me. If your plugin uses those hooks WordPress
   is letting you know that they won’t be relevant for the new editor. These types
   of notices should only appear if WP_DEBUG is enabled (Query Monitor might log
   these regardless, I’m not sure).
 * See the relevant section of the support docs here: [https://make.wordpress.org/support/handbook/appendix/using-wp_debug/#deprecated-functions-and-arguments](https://make.wordpress.org/support/handbook/appendix/using-wp_debug/#deprecated-functions-and-arguments)
 *  Thread Starter [Spiffy Plugins](https://wordpress.org/support/users/spiffyplugins/)
 * (@spiffyplugins)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/php-notices-in-post-editor/#post-10876327)
 * These notices are generated by core code, not by my plugin. I would think calls
   to these actions should be removed from core.
 *  Moderator [Ipstenu (Mika Epstein)](https://wordpress.org/support/users/ipstenu/)
 * (@ipstenu)
 * 🏳️‍🌈 Advisor and Activist
 * [7 years, 6 months ago](https://wordpress.org/support/topic/php-notices-in-post-editor/#post-10877885)
 * How did you determine the notices were from core code and not your plugin?
 *  Thread Starter [Spiffy Plugins](https://wordpress.org/support/users/spiffyplugins/)
 * (@spiffyplugins)
 * [7 years, 6 months ago](https://wordpress.org/support/topic/php-notices-in-post-editor/#post-10877908)
 * I disabled all plugins except Query Monitor and am using the Twenty Nineteen 
   theme.
 * I also did a search in the WordPress core and found:
 * – 3 calls to add_action( ‘edit_form_after_title’… ) in wp-admin\edit-form-advanced.
   php, wp-admin\includes\admin-filters.php and wp-admin\includes\meta-boxes.php
 * – 1 call to add_action( ‘edit_form_advanced’…) in wp-includes\class-wp-embed.
   php
 *  [davdebcom](https://wordpress.org/support/users/davdebcom/)
 * (@davdebcom)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/php-notices-in-post-editor/#post-10882920)
 * [@spiffyplugins](https://wordpress.org/support/users/spiffyplugins/) Did you 
   set this too resolved and if so, how did you resolve this? Getting the same notices
   without using those functions in my plugin.
 *  Thread Starter [Spiffy Plugins](https://wordpress.org/support/users/spiffyplugins/)
 * (@spiffyplugins)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/php-notices-in-post-editor/#post-10883633)
 * I did not set this to resolved.
 * I am still seeing the errors in WordPress 5.0-beta4-43896
 *  [davdebcom](https://wordpress.org/support/users/davdebcom/)
 * (@davdebcom)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/php-notices-in-post-editor/#post-10883760)
 * Me too.
 *  Moderator [Ipstenu (Mika Epstein)](https://wordpress.org/support/users/ipstenu/)
 * (@ipstenu)
 * 🏳️‍🌈 Advisor and Activist
 * [7 years, 5 months ago](https://wordpress.org/support/topic/php-notices-in-post-editor/#post-10884906)
 * I set it to resolved because it’s a known issue, and being worked on. Also keep
   in mind – DEPRECATED is not a required-right-now fix, just one that should be
   fixed before it’s removed. That’s why it’s a warning, not an error.
 * Also, Classic Editor is still in play, so WP has to support it for now. When (
   and IF) that’s removed it’ll get cleaned up.
 *  Thread Starter [Spiffy Plugins](https://wordpress.org/support/users/spiffyplugins/)
 * (@spiffyplugins)
 * [7 years, 5 months ago](https://wordpress.org/support/topic/php-notices-in-post-editor/#post-10910404)
 * FYI I still get one notice with 5.0-RC1-43944.
 * edit_form_advanced is deprecated since version 5.0.0! Use block_editor_meta_box_hidden_fields
   instead. This action is still supported in the classic editor, but is deprecated
   in the block editor.
 *  Moderator [Ipstenu (Mika Epstein)](https://wordpress.org/support/users/ipstenu/)
 * (@ipstenu)
 * 🏳️‍🌈 Advisor and Activist
 * [7 years, 5 months ago](https://wordpress.org/support/topic/php-notices-in-post-editor/#post-10911302)
 * I’ve mentioned that here – [https://core.trac.wordpress.org/ticket/45341](https://core.trac.wordpress.org/ticket/45341)–
   but again, it’s not ‘broken’ it’s just a warning.

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘PHP notices in post editor’ is closed to new replies.

 * In: [Alpha/Beta/RC](https://wordpress.org/support/forum/alphabeta/)
 * 10 replies
 * 4 participants
 * Last reply from: [Ipstenu (Mika Epstein)](https://wordpress.org/support/users/ipstenu/)
 * Last activity: [7 years, 5 months ago](https://wordpress.org/support/topic/php-notices-in-post-editor/#post-10911302)
 * Status: resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics