You can achieve this when you register your post types. The slug can be a path: $section_args = array( ‘rewrite’ => array( ‘slug’ => ‘help/section’ ), // your other args… ); $article_args = array( ‘rewrite’ => array( ‘slug’ => ‘help/article’ ), // your other args… );
It sounds like the plugin expects there to be a get param. Your rewrite-rule is removing the get-param before it can be used by the plugin. If the plugin hasn’t been updated for a long time (it’s abandonware) then you can go through the plugin and replace the get-param with the portion of the url … Read more
Try to add this one function add_rewrite_rules() { $newrules = array(‘^testrewrite/([0-9]+)/?’=> ‘index.php?page_id=$matches[1]’); return $newrules ; } add_filter(‘rewrite_rules_array’, ‘add_rewrite_rules’); Let me know it is working or not.
If you are needing one rewrite rule for that single page, this snippet should get you there. You’ll need to replace the XXXX in that snippet to be your post ID of your signup page. function signup_pg_rewrite_rule() { add_rewrite_rule(‘^signup/([^/]*)/?’,’index.php?page_id=XXXX&country_code=$matches[1]’,’top’); } add_action(‘init’, ‘signup_pg_rewrite_rule’, 10, 0); After you drop this in, you’ll need to flush that rewrite … Read more
The error 404 happens because you haven’t registered the %school% rewrite tag — you need to register it so that WordPress will know what to replace it with when generating the rewrite rules — i.e. it doesn’t remain as %school% in the generated rewrite rules. And you can register the tag using add_rewrite_tag(): // Add … Read more
You want display posts of a given type ({post_type}) from category ({term}) and structure of link should looks like this: {post_type} / category / {term} To avoid collisions with links to pages and “blog” posts, expression can not start with ([^/]+), but should contain slug of post type entered explicitly. This means a separate rule … Read more
The problem is with that add_rewrite_tag(‘%keyterms%’, ‘(.*)’), which results in rewrite conflicts because the generated rewrite rules would match http://example.com/(anything-here) and that (anything-here) can be a Page (post type page) slug, hence http://example.com/page-slug would not work — you wouldn’t get a 404 error page, but the proper Page wouldn’t be displayed, either. So looking at … Read more
You could do something like the following in .htaccess before the existing WordPress directives. RewriteCond %{QUERY_STRING} ^uri=(/[^&]+) RewriteRule ^nextgen-share/(\d+/\d+)/full$ %1#gallery/$1 [QSD,NE,R,L] The RewriteRule pattern only matches against the URL-path, so you need the preceding RewriteCond directive in order to match the query string portion of the URL. If the /121212/8989/ part always consists of 6 … Read more
You don’t need those custom rewrites and term permalink tweaks, so just remove these and the relevant callbacks: add_action(‘init’,’theme_child_custom_rewrite’, 1000); add_filter( ‘term_link’, ‘listing_region_term_link’, 1, 3 ); And just use the register_taxonomy_args hook to override the taxonomy’s parameters: function override_listing_region_taxonomy_args( $args, $taxonomy ) { if ( ‘listing-region’ === $taxonomy ) { $args[‘rewrite’] = array( ‘slug’ => … Read more
Here is an example of adding custom rewrite rule to WordPress. For instance, you have a link http://website.com/1/ that would like WordPress interprets internally as http://website.com?tl=1 But for tl you have mentioned, I am not sure what is your settings. So I assume tl is working in your system. Because WP default parameter is p … Read more