The SSL admin and login redirection should be done through the FORCE_SSL_ADMIN constant in wp-config.php: define(‘FORCE_SSL_ADMIN’, true); For further information: Administration Over SSL Aditionally, if you want be redirected to http when you’re logged and in the frontend, take a look at: Redirect WordPress front end https URLs to http without a plugin
When you register your taxonomy, set the slug parameter of rewrite to your desired structure: register_taxonomy( ‘custom_tax’, ‘custom_post_type’, array( ‘rewrite’ => array( ‘slug’ => ‘your-cpt-slug/category’ ), // your other args… ) );
In your register_post_type, you set ‘with_front’=> false, Later you declare the following function without arguments: add_permastruct( ‘review’, ‘reviews/%year%/%review%’); add_permastruct has an argument of with_front and the default value is true, which conflicts with your earlier declaration.
It wouldn’t work too smoothly since you are mixing “one of a thing” (which in WP usually means single post) and “many of a thing” (post or term archive). Since comments are engineered to work with posts (pages are also kind of a post), the closest to this you can easily get is probably creating … Read more
The short answer is: that’s not how rewrite rules work. You can see how they work in the examples section of the codex page. It sounds like what you’re trying to do is setup a redirect. I would suggest using a plugin to do that.
You are already using pages which does not work the same as posts. You have to remember, pages don’t have taxonomies and they are excluded from the main query by default on all archive pages and the homepage, so there can never be any links to any kind of archive. Archive pages, whether date, category … Read more
Let me say beforehand that when using add_rewrite_rule() nothing is written to the htaccess file. Rewrite rules are stored in the database and handled by WordPress internally on PHP level. TL;DR: Rewrite rules do persist after plugin deletion, but probably not the way you’d expect it. When using add_rewrite_rule these rules are added in the … Read more
You cannot do this with redirect. Since, by definition, redirect sends browser off to a different location. You would need to map domain to an actual WordPress installation. It’s not hard to have WP respond to different domain requests, however in your case it’s complicated that you would need it to respond differently conditional on … Read more
I think you shoud use some .htacess rexrite rules either than relying on the wordpress rewrite functions. It seems more appropriate in your case. Try a rule like this : RewriteRule ^root/([a-zA-Z]+)/([a-zA-Z]+)/$ /root/$2/ [R=301,L] Insert it right after RewriteBase /
after adding a new rule, you have to flush the rewrite-rules in order to use them that can be done with the “flush_rewrite_rules” function http://codex.wordpress.org/Function_Reference/flush_rewrite_rules or it can be done in going in the Administration Screens -> Settings -> Permalink and just saving without changing something on this screen