Eine auf WordPress spezialiserte Suchmaschine für Entwickler und Theme-Autoren



add_rewrite_endpoint ›

Seit2.1.0
Veraltetn/v
add_rewrite_endpoint ( $name, $places, $query_var = true )
Parameter: (3)
  • (string) $name Name of the endpoint.
    Erforderlich: Ja
  • (int) $places Endpoint mask describing the places the endpoint should be added.
    Erforderlich: Ja
  • (string|bool) $query_var Name of the corresponding query variable. Pass `false` to skip registering a query_var for this endpoint. Defaults to the value of `$name`.
    Erforderlich: Nein
    Standard: true
Definiert in:
Codex:
Changelog:
  • 4.3.0

Add an endpoint, like /trackback/.

Adding an endpoint creates extra rewrite rules for each of the matching places specified by the provided bitmask. For example:

add_rewrite_endpoint( 'json', EP_PERMALINK | EPPAGES );

will add a new rewrite rule ending with "json(/(.*))?/?$" for every permastruct that describes a permalink (post) or page. This is rewritten to "json=$match" where $match is the part of the URL matched by the endpoint regex (e.g. "foo" in "[permalink]/json/foo/").

A new query var with the same name as the endpoint will also be created.

When specifying $places ensure that you are using the EP* constants (or a combination of them using the bitwise OR operator) as their values are not guaranteed to remain static (especially EP_ALL).

Be sure to flush the rewrite rules - see flush_rewrite_rules() - when your plugin gets activated and deactivated.



Quellcode

function add_rewrite_endpoint( $name, $places, $query_var = true ) {
	global $wp_rewrite;
	$wp_rewrite->add_endpoint( $name, $places, $query_var );
}