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 |
|---|---|
| 442 | * is recommended to use PHP 5.X NTS. |
| 443 | * Next we check if the URL Rewrite Module 1.1 is loaded and enabled for the web site. When |
| 444 | * URL Rewrite 1.1 is loaded it always sets a server variable called 'IIS_UrlRewriteModule'. |
| 445 | * Lastly we make sure that PHP is running via FastCGI. This is important because if it runs |
| 446 | * via ISAPI then pretty permalinks will not work. |
| 447 | */ |
| 448 | $supports_permalinks = class_exists('DOMDocument') && isset($_SERVER['IIS_UrlRewriteModule']) && ( php_sapi_name() == 'cgi-fcgi' ); |
| 449 | } |
| 450 | |
| 451 | return apply_filters('iis7_supports_permalinks', $supports_permalinks); |
| 452 | } |
| 453 | |
| 454 | /** |
| 455 | * Check if rewrite rule for WordPress already exists in the IIS 7 configuration file |
| 456 | * |
| 457 | * @since 2.8.0 |
| 458 | * |
| 459 | * @return bool |
| 460 | * @param string $filename The file path to the configuration file |