You need to flush rewrite rules after adding or modifying rewrite rules in WordPress. flush_rewrite_rules() can be used to flush rules. For more info check these links : https://codex.wordpress.org/Rewrite_API/add_rewrite_rule https://codex.wordpress.org/Function_Reference/flush_rewrite_rules
From this other answer on the WP SE add_action(‘generate_rewrite_rules’, ‘roots_add_rewrites’); function roots_add_rewrites($content) { $theme_name = next(explode(‘/themes/’, get_stylesheet_directory())); global $wp_rewrite; $roots_new_non_wp_rules = array( ‘css/(.*)’ => ‘wp-content/themes/’. $theme_name . ‘/css/$1’, ‘js/(.*)’ => ‘wp-content/themes/’. $theme_name . ‘/js/$1’, ‘img/(.*)’ => ‘wp-content/themes/’. $theme_name . ‘/img/$1’, ); $wp_rewrite->non_wp_rules += $roots_new_non_wp_rules; } TheDeadMedic provided a much better version of this function: function … Read more
First you need to register your expected variables. Something similar to: function my_rewrite() { add_rewrite_tag(‘%ct_city%’, ‘([^&]+)’); add_rewrite_tag(‘%country%’, ‘([^&]+)’); } add_action(‘init’, ‘my_rewrite’, 10, 0); Then you need to create the rule which will redirect to your abm page. Note that you will need to discover your abm‘s ID, since you will need to pass it in … Read more
There are two types of rewrite rules you can generate via the API and add_rewrite_rule: internal rules and external rules. External rules get inserted into your .htaccess file, and must be in a format that can be parsed by Apache’s mod_rewrite. Internal rules get added to the WordPress internal rewrite rule array and must be … Read more
You only have one capture group, the ID is in matches[1], there is no matches[2]. EDIT- Here is the working version I tested in the 2016 theme. I created a page with slug sign-up, added the following to functions.php, then visited the Permalinks Settings page to flush rewrite rules. The value passed to product is … Read more
Terminology I think you have some terminology a little mixed up: A URL “rewrite” alters the endpoint of a HTTP request. If http://example.com/param/exam1 really serves content from http://example.com/examples/exam1?get=param, then the former is being rewritten to the latter (though not necessarily visible to the end-user). In the world of URL-rewriting, a “redirect” is a rewrite that … Read more
Use add_rewrite_rule to capture the url and convert to params internally. http://example.com/page{p}/t/{t} to http://example.com/?p={p}&t={t} Add to your function.php or in a plugin. <?php if ( ! class_exists( ‘SimpleRewrite’ ) ): class SimpleRewrite { const ENDPOINT_QUERY_NAME = ‘page’; const ENDPOINT_QUERY_PARAM = ‘__rewrite_page’; // WordPress hooks public function init() { add_filter( ‘query_vars’, array ( $this, ‘add_query_vars’ ), … Read more
Change your rewrite rules and the order to the following: add_rewrite_rule(‘my-url/([^/]*)/?$’, ‘index.php?my-var=$matches[1]’, ‘top’); add_rewrite_rule(‘my-url/?$’, ‘index.php?my-var=main’, ‘top’); Why the order? If the order would be the other way around, the first rule will always apply, so the ruleset would never reach your main page Why the changed syntax? To allow an additional query string to be … Read more
The way htaccess rewrite works (wp uses this), this drives the very first match on the list to load the targeted rewrite of URL. So answer to your question is YES, keep longer/elaborated rules at top, followed by less longer structures; alternatively you can write conditions (rewrite cond ) to match rules per blockwise.
It looks as though you are accidentally including -meaning inside your second match string. Instead of this: ^words/([^/]+)(?:/([0-9]+)-meaning)?/?$ … try this: ^words/([^/]+)(?:/([0-9]+))-meaning?/?$ And don’t forget to flush your permalinks after a change to the rules!