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 |
|---|---|
| 164 | * This filter differs from the post_class or body_class filters in two important ways: |
| 165 | * 1. $classes is a space-separated string of class names instead of an array. |
| 166 | * 2. Not all core admin classes are filterable, notably: wp-admin, wp-core-ui, and no-js cannot be removed. |
| 167 | * |
| 168 | * @since 2.3.0 |
| 169 | * |
| 170 | * @param string $classes Space-separated string of CSS classes. |
| 171 | */ |
| 172 | ?> |
| 173 | <body class="wp-admin wp-core-ui no-js <?php echo apply_filters( 'admin_body_class', '' ) . " $admin_body_class"; ?>"> |
| 174 | <script type="text/javascript"> |
| 175 | document.body.className = document.body.className.replace('no-js','js'); |
| 176 | </script> |
| 177 | |
| 178 | <?php |
| 179 | // Make sure the customize body classes are correct as early as possible. |
| 180 | if ( current_user_can( 'customize' ) ) { |
| 181 | wp_customize_support_script(); |
| 182 | } |