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 |
|---|---|
| 7584 | * @since 3.5.0 |
| 7585 | * @since 4.6.0 The default now takes the original `memory_limit` into account. |
| 7586 | * |
| 7587 | * @param int|string $filtered_limit Maximum memory limit to allocate for image processing. |
| 7588 | * Default `WP_MAX_MEMORY_LIMIT` or the original |
| 7589 | * php.ini `memory_limit`, whichever is higher. |
| 7590 | * Accepts an integer (bytes), or a shorthand string |
| 7591 | * notation, such as '256M'. |
| 7592 | */ |
| 7593 | $filtered_limit = apply_filters( 'image_memory_limit', $filtered_limit ); |
| 7594 | break; |
| 7595 | |
| 7596 | case 'cron': |
| 7597 | /** |
| 7598 | * Filters the memory limit allocated for WP-Cron event processing. |
| 7599 | * |
| 7600 | * @since 6.3.0 |
| 7601 | * |
| 7602 | * @param int|string $filtered_limit Maximum memory limit to allocate for WP-Cron. |