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 |
|---|---|
| 7177 | * (256 megabytes of memory) or the original `memory_limit` php.ini value if |
| 7178 | * this is higher. |
| 7179 | * |
| 7180 | * @since 3.0.0 |
| 7181 | * @since 4.6.0 The default now takes the original `memory_limit` into account. |
| 7182 | * |
| 7183 | * @param int|string $filtered_limit The maximum WordPress memory limit. Accepts an integer |
| 7184 | * (bytes), or a shorthand string notation, such as '256M'. |
| 7185 | */ |
| 7186 | $filtered_limit = apply_filters( 'admin_memory_limit', $filtered_limit ); |
| 7187 | break; |
| 7188 | |
| 7189 | case 'image': |
| 7190 | /** |
| 7191 | * Filters the memory limit allocated for image manipulation. |
| 7192 | * |
| 7193 | * @since 3.5.0 |
| 7194 | * @since 4.6.0 The default now takes the original `memory_limit` into account. |
| 7195 | * |