It looks like you need to process the rewrite using query strings rather than a URI segment and pass your query through index.php. WordPress seems to be agnostic of what you’re trying to accomplish here. Try the following rule and visit your Settings->Permalinks page to flush previous rules and add this to the stack. add_rewrite_rule( … Read more
When creating a custom post type you can define the slug using the argument “rewrite” http://codex.wordpress.org/Function_Reference/register_post_type or you could use a plugin http://wordpress.org/extend/plugins/custom-post-type-permalinks/
This is currently not possible for a multisite setup. It should be possible in WordPress 3.5 which is planned to be released next month. So your only solution is: wait. Update December 26: This is now possible in WordPress 3.5 without further hacks. 🙂
Redirection allows you to modify post slugs and keeps a history of them, pointing all requests for the history of a page to the same destination. It’s useful for all sorts of other things too, but it will definitely solve this problem.
Honestly, can not debug your code, but this one works: function register_crr_jsonwebservice( $wp_rewrite ) { //Add the rewrite rule for this specific json controller add_rewrite_tag( ‘%ticket%’, ‘([a-zA-Z0-9]+)’); $wp_rewrite->rules = array( ‘cjson/fullticket/?([a-zA-Z0-9]{1,})/?$’ => $wp_rewrite->index . “?page_id=243&ticket=”.$matches[1] ) + $wp_rewrite->rules; } add_action( ‘generate_rewrite_rules’, ‘register_crr_jsonwebservice’ ); Do not call flush_rewrite_rules(); from this function – will lead to an … Read more
You’re not doing anything wrong. WordPress does not monitor the links within content, so it’s up to you to change them when your structure changes.
I believe this article may help you. http://vocecommunications.com/blog/2010/11/adding-rewrite-rules-for-custom-post-types/ I think what you’re missing is in the third section, where she’s making a redirect rule (I think your site isn’t redirecting correctly because it’s missing a rule to do so…)
You can use add_rewrite_endpoint, which will add a query var and generate the necessary rewrite rules: function wpd_cid_endpoint() { add_rewrite_endpoint( ‘cid’, EP_PERMALINK ); } add_action( ‘init’, ‘wpd_cid_endpoint’ ); Don’t forget to flush rewrite rules after changing rules. You can do this quickly by visiting the Settings > Permalinks page in admin.
RewriteCond %{HTTP_HOST} dom1 [NC] RewriteRule ^((about\-us|etc).*) /dom1/$1 [NC,QSA,L] Your rewrite rule includes the L parameter, which makes it stop processing rewrites. So WordPress’s rules to redirect to index.php likely never come into effect. Which means WordPress is not even being run here. The 404 is likely from the webserver saying that the file at /dom1/about-us … Read more
Your rewrite setting is good, but WordPress are redirect to the canonical url of the post. This is done by WodPress to prevent bad indexing for duplicate content (when an identical content is accessible via 2 different urls). You can prevent that removing the canonical redirect filter: add_action(‘wp_loaded’, function() { remove_filter(‘template_redirect’, ‘redirect_canonical’); }); However this … Read more