Title: &#8216;get_current_screen&#8217; called before admin_init hook
Last modified: March 31, 2026

---

# ‘get_current_screen’ called before admin_init hook

 *  Resolved [janevolve](https://wordpress.org/support/users/janevolve/)
 * (@janevolve)
 * [1 month, 3 weeks ago](https://wordpress.org/support/topic/get_current_screen-called-before-admin_init-hook/)
 * For time to time, after the plugin gets updated, we need to manually “patch” 
   the plugin cause it keeps breaking due function “**get_current_screen**” getting
   called in “**admin_menu**” hook which trigger before “**admin_init**“.
 * “**get_current_screen**” only gets available after “**admin_init**” has fired.
   [ref](https://developer.wordpress.org/reference/functions/get_current_screen/#comment-5424)
 * “**admin_menu**” fires before “**admin_init**“. [ref](https://developer.wordpress.org/reference/hooks/admin_menu/)
 * “**get_current_screen**” is called inside **TO_Terms_Walker** class, **start_el**
   method.

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

 *  Plugin Author [Maya](https://wordpress.org/support/users/tdgu/)
 * (@tdgu)
 * [1 month, 3 weeks ago](https://wordpress.org/support/topic/get_current_screen-called-before-admin_init-hook/#post-18869298)
 * Hi,
   Thanks for your feedback.I’am not sure how the **get_current_screen**() is
   triggering the error for you, in the **TO_Terms_Walker** class, as this is called
   after admin_init has triggered. That interface is invoked through add_submenu_page()
   WordPress method, which triggers the argument after the admin_init action has
   been executed. Maybe there is a specific step you took to replicate the error?
   Is this always occours for you ? Maybe a different code interefers with the **
   get_current_screen**() methodThanks
 *  Thread Starter [janevolve](https://wordpress.org/support/users/janevolve/)
 * (@janevolve)
 * [1 month, 3 weeks ago](https://wordpress.org/support/topic/get_current_screen-called-before-admin_init-hook/#post-18873165)
 * Im closing this now, since this seems to be a poor implementation on our end 
   when trying to extend plugin functionality to custom frontend.

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

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fget_current_screen-called-before-admin_init-hook%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/taxonomy-terms-order/assets/icon-256x256.png?rev=1564412)
 * [Category Order and Taxonomy Terms Order](https://wordpress.org/plugins/taxonomy-terms-order/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/taxonomy-terms-order/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/taxonomy-terms-order/)
 * [Active Topics](https://wordpress.org/support/plugin/taxonomy-terms-order/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/taxonomy-terms-order/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/taxonomy-terms-order/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [janevolve](https://wordpress.org/support/users/janevolve/)
 * Last activity: [1 month, 3 weeks ago](https://wordpress.org/support/topic/get_current_screen-called-before-admin_init-hook/#post-18873165)
 * Status: resolved