Changeset 34939
 Timestamp:
 10/08/2015 04:46:16 PM (5 years ago)
 File:

 1 edited
Legend:
 Unmodified
 Added
 Removed

trunk/src/wpincludes/classwprewrite.php
r34938 r34939 164 164 * 165 165 * If PATHINFO/index permalinks are in use then the root is the value of 166 * {@link WP_Rewrite::$index} with a trailing slash appended. Otherwise167 * the rootwill be empty.166 * `WP_Rewrite::$index` with a trailing slash appended. Otherwise the root 167 * will be empty. 168 168 * 169 169 * @see WP_Rewrite::init() … … 227 227 * 228 228 * These rules are written to the mod_rewrite portion of the .htaccess, 229 * and are added by {@link add_external_rule()}.229 * and are added by add_external_rule(). 230 230 * 231 231 * @since 2.1.0 … … 236 236 237 237 /** 238 * Extra permalink structures, e.g. categories, added by {@link add_permastruct()}.238 * Extra permalink structures, e.g. categories, added by add_permastruct(). 239 239 * 240 240 * @since 2.1.0 … … 245 245 246 246 /** 247 * Endpoints (like /trackback/) added by {@link add_rewrite_endpoint()}.247 * Endpoints (like /trackback/) added by add_rewrite_endpoint(). 248 248 * 249 249 * @since 2.1.0 … … 273 273 * set to true. Prior to WordPress 3.3 this flag indicated that every page 274 274 * would have a set of rules added to the top of the rewrite rules array. 275 * Now it tells {@link WP::parse_request()} to check if a URL matching the 276 * page permastruct is actually a page before accepting it. 277 * 278 * @link https://core.trac.wordpress.org/ticket/16687 275 * Now it tells WP::parse_request() to check if a URL matching the page 276 * permastruct is actually a page before accepting it. 277 * 278 * @since 2.5.0 279 * @access public 280 * @var bool 281 * 279 282 * @see WP_Rewrite::init() 280 * @since 2.5.0281 * @access public282 * @var bool283 283 */ 284 284 public $use_verbose_page_rules = true; … … 288 288 * 289 289 * These are translated into the regular expressions stored in 290 * {@link WP_Rewrite::$rewritereplace} and are rewritten to the291 * query variables listed in {@link WP_Rewrite::$queryreplace}.292 * 293 * Additional tags can be added with {@link add_rewrite_tag()}.290 * `WP_Rewrite::$rewritereplace` and are rewritten to the query 291 * variables listed in WP_Rewrite::$queryreplace. 292 * 293 * Additional tags can be added with add_rewrite_tag(). 294 294 * 295 295 * @since 1.5.0 … … 313 313 /** 314 314 * Regular expressions to be substituted into rewrite rules in place 315 * of rewrite tags, see {@link WP_Rewrite::$rewritecode}.315 * of rewrite tags, see WP_Rewrite::$rewritecode. 316 316 * 317 317 * @since 1.5.0 … … 334 334 335 335 /** 336 * Query variables that rewrite tags map to, see {@link WP_Rewrite::$rewritecode}.336 * Query variables that rewrite tags map to, see WP_Rewrite::$rewritecode. 337 337 * 338 338 * @since 1.5.0 … … 1139 1139 * Generate Rewrite rules with permalink structure and walking directory only. 1140 1140 * 1141 * Shorten version of {@link WP_Rewrite::generate_rewrite_rules()} that 1142 * allows for shorter list of parameters. See the method for longer 1143 * description of what generating rewrite rules does. 1144 * 1145 * @uses WP_Rewrite::generate_rewrite_rules() See for long description and rest of parameters. 1146 * @since 1.5.0 1147 * @access public 1141 * Shorten version of WP_Rewrite::generate_rewrite_rules() that allows for shorter 1142 * list of parameters. See the method for longer description of what generating 1143 * rewrite rules does. 1144 * 1145 * @since 1.5.0 1146 * @access public 1147 * 1148 * @see WP_Rewrite::generate_rewrite_rules() See for long description and rest of parameters. 1148 1149 * 1149 1150 * @param string $permalink_structure The permalink structure to generate rules. … … 1364 1365 * Retrieve the rewrite rules. 1365 1366 * 1366 * The difference between this method and {@link 1367 * WP_Rewrite::rewrite_rules()} is that this method stores the rewrite rules 1368 * in the 'rewrite_rules' option and retrieves it. This prevents having to 1369 * process all of the permalinks to get the rewrite rules in the form of 1370 * caching. 1367 * The difference between this method and WP_Rewrite::rewrite_rules() is that 1368 * this method stores the rewrite rules in the 'rewrite_rules' option and retrieves 1369 * it. This prevents having to process all of the permalinks to get the rewrite rules 1370 * in the form of caching. 1371 1371 * 1372 1372 * @since 1.5.0 … … 1623 1623 * Add a new permalink structure. 1624 1624 * 1625 * A permalink structure (permastruct) is an abstract definition of a set of rewrite rules; it1626 * i s an easy way of expressing a set of regular expressions that rewrite to a set of query strings.1627 * The new permastruct is added to the {@link WP_Rewrite::$extra_permastructs} array. When the1628 * rewrite rules are built by {@link WP_Rewrite::rewrite_rules()} all of these extra permastructs1629 * are passed to {@link WP_Rewrite::generate_rewrite_rules()} which transforms them into the1630 * regular expressions that many love to hate.1631 * 1632 * The $args parameter gives you control over how {@link WP_Rewrite::generate_rewrite_rules()}1625 * A permalink structure (permastruct) is an abstract definition of a set of rewrite rules; 1626 * it is an easy way of expressing a set of regular expressions that rewrite to a set of 1627 * query strings. The new permastruct is added to the WP_Rewrite::$extra_permastructs array. 1628 * When the rewrite rules are built by WP_Rewrite::rewrite_rules(), all of these extra 1629 * permastructs are passed to WP_Rewrite::generate_rewrite_rules() which transforms them 1630 * into the regular expressions that many love to hate. 1631 * 1632 * The `$args` parameter gives you control over how WP_Rewrite::generate_rewrite_rules() 1633 1633 * works on the new permastruct. 1634 1634 * … … 1679 1679 * Remove rewrite rules and then recreate rewrite rules. 1680 1680 * 1681 * Calls {@link WP_Rewrite::wp_rewrite_rules()} after removing the 1682 * 'rewrite_rules' option. If the function named 'save_mod_rewrite_rules' 1683 * exists, it will be called. 1681 * Calls WP_Rewrite::wp_rewrite_rules() after removing the 'rewrite_rules' option. 1682 * If the function named 'save_mod_rewrite_rules' exists, it will be called. 1684 1683 * 1685 1684 * @since 2.0.1 … … 1762 1761 * Will update the 'permalink_structure' option, if there is a difference 1763 1762 * between the current permalink structure and the parameter value. Calls 1764 * {@link WP_Rewrite::init()}after the option is updated.1763 * WP_Rewrite::init() after the option is updated. 1765 1764 * 1766 1765 * Fires the 'permalink_structure_changed' action once the init call has … … 1794 1793 * 1795 1794 * Will update the 'category_base' option, if there is a difference between 1796 * the current category base and the parameter value. Calls 1797 * {@link WP_Rewrite::init()}after the option is updated.1795 * the current category base and the parameter value. Calls WP_Rewrite::init() 1796 * after the option is updated. 1798 1797 * 1799 1798 * @since 1.5.0 … … 1813 1812 * 1814 1813 * Will update the 'tag_base' option, if there is a difference between the 1815 * current tag base and the parameter value. Calls 1816 * {@link WP_Rewrite::init()} afterthe option is updated.1814 * current tag base and the parameter value. Calls WP_Rewrite::init() after 1815 * the option is updated. 1817 1816 * 1818 1817 * @since 2.3.0
Note: See TracChangeset
for help on using the changeset viewer.