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 |
|---|---|
| 7868 | * their own contexts for raising the memory limit. |
| 7869 | * |
| 7870 | * @since 4.6.0 |
| 7871 | * |
| 7872 | * @param int|string $filtered_limit Maximum memory limit to allocate for this context. |
| 7873 | * Default WP_MAX_MEMORY_LIMIT` or the original php.ini `memory_limit`, |
| 7874 | * whichever is higher. Accepts an integer (bytes), or a |
| 7875 | * shorthand string notation, such as '256M'. |
| 7876 | */ |
| 7877 | $filtered_limit = apply_filters( "{$context}_memory_limit", $filtered_limit ); |
| 7878 | break; |
| 7879 | } |
| 7880 | |
| 7881 | $filtered_limit_int = wp_convert_hr_to_bytes( $filtered_limit ); |
| 7882 | |
| 7883 | if ( -1 === $filtered_limit_int || ( $filtered_limit_int > $wp_max_limit_int && $filtered_limit_int > $current_limit_int ) ) { |
| 7884 | if ( false !== ini_set( 'memory_limit', $filtered_limit ) ) { |
| 7885 | return $filtered_limit; |
| 7886 | } else { |