Source View: rewrite_rules

To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).

Understanding Source Code

The best way to understand what a hook does is to look at where it occurs in the source code.

  • Action hooks look like this: do_action( "hook_name" )
  • Filter hooks look like this: 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.

Source View

Line Code
1696           } else {
1697                $rules .= "RewriteCond %{REQUEST_FILENAME} !-f\n" .
1698                     "RewriteCond %{REQUEST_FILENAME} !-d\n" .
1699                     "RewriteRule . {$home_root}{$this->index} [L]\n";
1700           }
1701
1702           $rules .= "</IfModule>\n";
1703
1704           $rules = apply_filters('mod_rewrite_rules', $rules);
1705           $rules = apply_filters('rewrite_rules', $rules);  // Deprecated
1706
1707           return $rules;
1708      }
1709
1710      /**
1711       * Retrieve IIS7 URL Rewrite formatted rewrite rules to write to web.config file.
1712       *
1713       * Does not actually write to the web.config file, but creates the rules for
1714       * the process that will.