I’m not sure if this is the only reason why it wasn’t working but I was missing two things. I wasn’t added any sort of rewrite rule to test on I was testing against pagename instead of query_vars. Here’s the final solution: /** Register Query Vars **/ function theme_custom_query_vars( $vars ){ $vars[] = ‘map’; return … Read more
I ended up following @Kolya Korobochkin advice and added uppercase and lowercase versions of the rewrite rules that include escaped octets. $regular_page_uri = get_page_uri( $page->ID ); $uppercase_page_uri = preg_replace_callback( ‘/%[0-9a-zA-Z]{2}/’, create_function( ‘$x’, ‘return strtoupper( $x[0] );’ ), $regular_page_uri ); The Percent Encode Capital Letter plugin uses a similar approach to convert the octets in every … Read more
OK, let’s first get some definitive clarification on the proper query vars. Refer to Post and Page parameters on the WP_Query codex page. name (string) – use post slug. pagename (string) – use page slug. We can confirm this with WP_Query: $args = array( ‘name’ => ‘mypage’ ); $mypage = new WP_Query( $args ); echo … Read more
There are two different rewrite systems at play when you have pretty permalinks enabled. The first is Apache’s mod_rewrite, which basically sends any request that isn’t for a physical directory or file to the main WordPress index.php file. The second system is internal to WordPress, and handles conversion of pretty permalinks into their component query … Read more
I want to remove all instances on aff=x regardless of how many other parameters in the URL. Assuming you want to keep any other URL parameters (in any order) and simply remove the aff=number parameter, then you can do something like the following using mod_rewrite in the root .htaccess file: RewriteCond %{QUERY_STRING} ^(.*&|)aff=\d+(?:&(.*)|)$ RewriteRule (.*) … Read more
Solved by this lines: RewriteEngine On RewriteBase / RewriteRule ^wp-json/(.*) /?rest_route=/$1 [L]
Your permalink structure for taxonomy will conflict with default one for pages. In the case of the address domain.com/item-one/item-two how does WordPress know if it’s a page item-two with the parent page item-one or item-two is custom post type and item-one is term of region taxonomy? The order of rewrite rules will decide, and because … Read more
Rather than modifying stored rules it would be more reliable to modify rules before they are stored. flush_rewrite_rules() calls WP_Rewrite->flush_rules() WP_Rewrite->wp_rewrite_rules() WP_Rewrite->rewrite_rules() Inside last there are fitting hooks to modify rules (after which result they will be saved as usual on each flush): do_action_ref_array(‘generate_rewrite_rules’, array(&$this)); $this->rules = apply_filters(‘rewrite_rules_array’, $this->rules);
You have to build up the link structure by using filters post_link and post_type_link: add_filter(‘post_link’, ‘territorio_permalink’, 10, 3); add_filter(‘post_type_link’, ‘territorio_permalink’, 10, 3); function territorio_permalink($permalink, $post_id, $leavename) { if (strpos($permalink, ‘%territorio%’) === FALSE) return $permalink; // Get post $post = get_post($post_id); if (!$post) return $permalink; // Get taxonomy terms $terms = wp_get_object_terms($post->ID, ‘territorio’,’orderby=term_order’); if (!is_wp_error($terms) && … Read more
You are doing everything right, double check the below code and make sure to go to Permalinks in your dashboard to flush the rewrite rules. From WordPress Codex: Note: Visiting the Permalinks screen triggers a flush of rewrite rules. There is no need to save just to flush the rewrite rules. It will work, I … Read more