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 |
|---|---|
| 2772 | /** |
| 2773 | * Filters attributes to be added to a script tag. |
| 2774 | * |
| 2775 | * @since 5.7.0 |
| 2776 | * |
| 2777 | * @param array $attributes Key-value pairs representing `<script>` tag attributes. |
| 2778 | * Only the attribute name is added to the `<script>` tag for |
| 2779 | * entries with a boolean value, and that are true. |
| 2780 | */ |
| 2781 | $attributes = apply_filters( 'wp_script_attributes', $attributes ); |
| 2782 | |
| 2783 | return sprintf( "<script%s></script>\n", wp_sanitize_script_attributes( $attributes ) ); |
| 2784 | } |
| 2785 | |
| 2786 | /** |
| 2787 | * Prints formatted `<script>` loader tag. |
| 2788 | * |
| 2789 | * It is possible to inject attributes in the `<script>` tag via the {@see 'wp_script_attributes'} filter. |
| 2790 | * Automatically injects type attribute if needed. |