You’re missing the WP $matches[1] syntax for the regex that gets matched. I think you want /? on the end too. Easiest way I found to test was to temporarily put flush_rewrite_rules() in whilst testing, then you don’t have to do anything else. I have a similar regex which sends /foo/catname/ to index.php?taxonomy=category&term=catname, here’s what … Read more
It doesn’t work with add_rewrite_rule() because of the ?view= part in the URL (it’s the first parameter for the function) — i.e. WordPress strips that query string part, hence it’s not included when WordPress finds a matching rewrite rule. how I can remove ?view=12a34b56 after set post name You can’t (not on the same page), … Read more
I just hit this issue as well and realised I had: define( ‘PATH_CURRENT_SITE’, ” ); in one of my configs and it should’ve been: define( ‘PATH_CURRENT_SITE’, “https://wordpress.stackexchange.com/” );
Why it happens The error 404 on the th/<page slug> pages occurs because your custom rewrite rules overwrite the default Page rules which would otherwise load the correct Page (having the slug <page slug>). How to fix the issue If your permalink structure is /%postname%, i.e. example.com/<post slug>, then a simple fix to the error … Read more
I believe I’ve found the solution. I add the following RewriteRule ^example_directory/files/(.*) new_directory/$1 to my WordPress .htaccess rules like so: RewriteEngine On RewriteBase / RewriteRule ^example_directory/files/(.*) new_directory/$1 RewriteRule ^index\.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] I couldn’t get it working before and I think the key was moving the … Read more
You can “workaround” the issue with a redirect in .htaccess, although it’s not clear why this double-domain-URL would be accessible in the first place. So, we can redirect URLs of the form example.com/example.com/?cat=6 to example.com/?cat=6, which you then say is correctly redirected to example.com/category by WordPress. For example, at the top of your .htaccess file: … Read more
As it says in the file: The directives (lines) between “BEGIN WordPress” and “END WordPress” are dynamically generated, and should only be modified via WordPress filters. Any changes to the directives between these markers will be overwritten. Put your code before #BEGIN WordPress or after # END WordPress. However, in the [L] flag means LAST, … Read more
I ended up with this: // Register Custom Taxonomy function fixed_tags_taxonomy() { $labels = array( ‘name’ => _x( ‘Fixed Tags’, ‘Taxonomy General Name’, ‘text_domain’ ), ‘singular_name’ => _x( ‘Fixed Tag’, ‘Taxonomy Singular Name’, ‘text_domain’ ), ); $args = array( ‘labels’ => $labels, ‘hierarchical’=>true, ); register_taxonomy( ‘fixed-tags’, array( ‘portfolio’ ), $args ); } add_action( ‘init’, __NAMESPACE__ … Read more
Or you could just add the relevant directive to the top of the .htaccess file directly. For example: RewriteRule ^([^/]+)\.html$ /product/$1 [R=302,L] This matches /anyname.html (as in your example), but not /foo/bar/anyname.html.
The problem is that I used the wrong type of quote marks. You cannot see it in my first post because apparently they were changed when I pasted in the code.