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
Query vars don’t end up in $_GET, use get_query_var() to fetch or check the value of your custom query vars set by rewrite rules. Your rule is currently returning employees as employees_slug because your rule has two capture groups, so employees_slug is held in $matches[2], not $matches[1]. The first capture group is unnecessary though, so … 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
Thank to @Milo I was able to solve this 1) Delete anything that might be reserving /blog/ url. In my case, It was a singular page with URL /blog/. 2) Modify custom post type declaration so it has ‘has_archive’ => true 3) Create archive-blog.php and move your code here. (You can just use global query … Read more
You should try the Rewrite plugin as mentioned in this post “Nginx rewrite rule conflict with WordPress permalinks rule“, it could help solve the issue. If not, we’ll have to dig deeper, let me know.
The problem must be how you define your post variable. You assume it’s the global $post but that’s not always the case especially in non-singular pages like archives. The filter itself provides the correct post instance that’s it’s been called on as 2nd parameter. function product_type_permalink( $post_link, $post ) { // current post is already … Read more
You need to use %cities% (matching the name of the taxonomy). I thought that %city% was just a placeholder with a random name. Not quite – it’s called a permalink structure (permastruct) and is used to map to a regular expression. When you call register_taxonomy, it automatically registers a new permastruct with the same name … Read more
The User data of the currently logged in user in WordPress can be retrieved via wpget_current_user() So you should be able to do something like this in your theme or wherever. $current_user = wp_get_current_user(); echo ‘<a href=”http://example.com/members/’ . $current_user->user_login . ‘/profile”>Your profile</a>.’; And build your link that way. HTH
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!
You need to either go into Settings -> Permalinks and click Save Or if you’re doing this programmatically you need to use flush_rewrite_rules(), but make sure this is only used when you activate/deactivate the plugin, DON’T set this in code that runs (like in init, or on every page load): https://developer.wordpress.org/reference/functions/flush_rewrite_rules/ register_deactivation_hook( __FILE__, ‘flush_rewrite_rules’ ); … Read more