Need help with rewrite_rules_array

5 Views

I have a page that I access at /category/tasks and the file is located at wp-content/themes/my-theme/tasks.php. I would like to make it so I can add a flag after tasks and pick up the query strong in tasks.php. This works fine when I access the page with /category/tasks/?when=upcoming.

Can someone tell me how to use rewrite_rules_array so it will send the variable through the query string using the URL structure /category/tasks/upcoming?

Post Views: 5

Related posts

Leave a Reply

3 comments

  1. Try this:

    function when_rewrite_rules( $wp_rewrite ) {
  $new_rules = array();
  $new_rules['category/tasks/(d*)$'] = 'index.php?when=$matches[1]';
  $wp_rewrite->rules = $new_rules + $wp_rewrite->rules;
}
add_filter('generate_rewrite_rules','when_rewrite_rules');

  2. It’s not very hard. You add a new rewrite rule that accepts your URL format and sets the correct query vars (you can choose any name you want, as long as it is unique). There are many ways to add rewrite rules, I prefer add_rewrite_rule(). Be sure to flush the rules once after you do this (from your code, or by visiting the Permalinks page).

    add_action( 'init', 'wpse8764_init' );
function wpse8764_init()
{
    add_rewrite_rule( 'category/tasks/upcoming/?$', 'index.php?pagename=category/tasks&wpse8764_var=upcoming', 'top' );
}

    This query variable will not be passed on to $wp_query unless you add it to the public query vars. After this, you can access it with get_query_var( 'wpse8764_var' ).

    add_filter( 'query_vars', 'wpse8764_query_vars' );
function wpse8764_query_vars( $query_vars )
{
    $query_vars[] = 'wpse8764_var';
    return $query_vars;
}

  3. There’s a permalink endpoint feature but it’s very broken when used without a trailing parameter.

    For one, there is this issue, which is only fixed to the extent that they’ve amended the docs:

    http://core.trac.wordpress.org/ticket/9476

    But most importantly, the rewrite engine uses empty() at one point, detects the endpoint as empty as a result, and does mark it as set anywhere as a result. There are three workarounds.

    One is what you’re apparently doing at the moment, aka pass a GET parameter.

    Another is to hook onto init and then adjust a global and change the REQUEST_URI accordingly when you detect your end point.

    The last is to actually use a parameter, i.e. not:

    /category/tasks/upcoming

    but rather:

    /category/tasks/filter/upcoming