RedirectMatch of Mod_Alias is not as powerful as Mod_Rewrite. If you have Mod_Rewrite on your host (Pretty Permalinks make use of it for example) you could make the redirect only if the URL is not in the Archive link format. To test for that case, there is RewriteCond and to make the redirect command, there … Read more
I solved it myself.. It was issue in the windows server with wordpress 3.1 so i installed the Permalink fix pack @ wordpress.org/extend/plugins/… . Now its working fine.. I’ve no issues linux server.. I’ve to dive into the thing to know why that is happening in windows server…
I would setup two WP installations at: /consumers/ /business/ Then you just need to share the theme between the two, adding switch statements to a single installation or trying to amend the rewrite structure can get messy quickly. The example.com homepage can just be a simple HTML page allowing the customer to link between the … Read more
OK. It appears it was a cookie path problem. I eventually solved it by adding @define( ‘ADMIN_COOKIE_PATH’, “https://wordpress.stackexchange.com/” ); to the start of wp-config.php – as suggested by AppFlak. The vital clue came from monitoring the output of wp_parse_auth_cookie() under various states. Thanks for the ideas, guys! Makes it a lot easier with extra brains … Read more
yes, this: https?://yoursite.com doesn’t do anything you want, just make it http://yoursite.com. Next to that, make sure your server actually supports RedirectMatch.
A quick fix could be to change the permissions on your .htaccess file so if you change settings in WordPress, it’ll show you what you need to manually change your .htaccess to since it won’t have direct write access to the file anymore.
Does a double install sound feasible and the right approach? Given your restrictions, yes…I can’t think of any other way to do it with a single install. If there was a way to get the legacy software to control member accounts via any other system (perhaps dumping to a CSV which can then be read … Read more
You’re correct, when you update the permalinks, the htaccess file also updates. When you create or update a “pretty” permalink structure, WordPress will generate rewrite rules and attempt to insert them into the proper .htaccess file. If it can’t, it will say something like “You should update your .htaccess now” and print out the rules … Read more
Due to WP admin architecture this would be really inconvenient list to compile and maintain reliably. My best educated guess is that many (but possibly not all and not just) of these files would need to require admin bootstrap (wp-admin/admin.php) to function. I ran a quick search on respective directive with following results: C:\server\www\dev\wordpress\src>ack –files-with-matches … Read more
If you want to block direct access to the other folder, you can put a .htaccess file in that folder that contains just: deny from all That way you cannot open any file from that folder directly, but you can include them (in PHP) without any problems.