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 |
|---|---|
| 7487 | * @since 3.5.0 |
| 7488 | * @since 4.6.0 The default now takes the original `memory_limit` into account. |
| 7489 | * |
| 7490 | * @param int|string $filtered_limit Maximum memory limit to allocate for images. |
| 7491 | * Default `WP_MAX_MEMORY_LIMIT` or the original |
| 7492 | * php.ini `memory_limit`, whichever is higher. |
| 7493 | * Accepts an integer (bytes), or a shorthand string |
| 7494 | * notation, such as '256M'. |
| 7495 | */ |
| 7496 | $filtered_limit = apply_filters( 'image_memory_limit', $filtered_limit ); |
| 7497 | break; |
| 7498 | |
| 7499 | default: |
| 7500 | /** |
| 7501 | * Filters the memory limit allocated for arbitrary contexts. |
| 7502 | * |
| 7503 | * The dynamic portion of the hook name, `$context`, refers to an arbitrary |
| 7504 | * context passed on calling the function. This allows for plugins to define |
| 7505 | * their own contexts for raising the memory limit. |