WP hooks navigation: Home/browse • Actions index • Filters index
To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).
The best way to understand what a hook does is to look at where it occurs in the source code.
do_action( "hook_name" )apply_filters( "hook_name", "what_to_filter" ).Remember, this hook may occur in more than one file. Moreover, the hook's context may change from version to version.
| Line | Code |
|---|---|
| 123 | * handled separately. |
| 124 | * |
| 125 | * The WP_MAX_MEMORY_LIMIT constant specifically defines the maximum memory limit available |
| 126 | * when in the administration back-end. The default is 256M, or 256 megabytes of memory. |
| 127 | * |
| 128 | * @since 3.0.0 |
| 129 | * |
| 130 | * @param string 'WP_MAX_MEMORY_LIMIT' The maximum WordPress memory limit. Default 256M. |
| 131 | */ |
| 132 | @ini_set( 'memory_limit', apply_filters( 'admin_memory_limit', WP_MAX_MEMORY_LIMIT ) ); |
| 133 | } |
| 134 | |
| 135 | /** |
| 136 | * Fires as an admin screen or script is being initialized. |
| 137 | * |
| 138 | * Note, this does not just run on user-facing admin screens. |
| 139 | * It runs on admin-ajax.php and admin-post.php as well. |
| 140 | * |
| 141 | * This is roughly analgous to the more general 'init' hook, which fires earlier. |