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 |
|---|---|
| 2806 | /** |
| 2807 | * Filters attributes to be added to a script tag. |
| 2808 | * |
| 2809 | * @since 5.7.0 |
| 2810 | * |
| 2811 | * @param array $attributes Key-value pairs representing `<script>` tag attributes. |
| 2812 | * Only the attribute name is added to the `<script>` tag for |
| 2813 | * entries with a boolean value, and that are true. |
| 2814 | */ |
| 2815 | $attributes = apply_filters( 'wp_script_attributes', $attributes ); |
| 2816 | |
| 2817 | return sprintf( "<script%s></script>\n", wp_sanitize_script_attributes( $attributes ) ); |
| 2818 | } |
| 2819 | |
| 2820 | /** |
| 2821 | * Prints formatted `<script>` loader tag. |
| 2822 | * |
| 2823 | * It is possible to inject attributes in the `<script>` tag via the {@see 'wp_script_attributes'} filter. |
| 2824 | * Automatically injects type attribute if needed. |