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 |
|---|---|
| 2722 | * Filters attributes to be added to a script tag. |
| 2723 | * |
| 2724 | * @since 5.7.0 |
| 2725 | * |
| 2726 | * @param array $attributes Key-value pairs representing `<script>` tag attributes. |
| 2727 | * Only the attribute name is added to the `<script>` tag for |
| 2728 | * entries with a boolean value, and that are true. |
| 2729 | * @param string $javascript Inline JavaScript code. |
| 2730 | */ |
| 2731 | $attributes = apply_filters( 'wp_inline_script_attributes', $attributes, $javascript ); |
| 2732 | |
| 2733 | $javascript = "\n" . trim( $javascript, "\n\r " ) . "\n"; |
| 2734 | |
| 2735 | return sprintf( "<script%s>%s</script>\n", wp_sanitize_script_attributes( $attributes ), $javascript ); |
| 2736 | } |
| 2737 | |
| 2738 | /** |
| 2739 | * Prints inline JavaScript wrapped in `<script>` tag. |
| 2740 | * |