This is fairly easy to set up using virtual host configurations in Apache or Nginx (depending on which webserver you want to run on your box). Here’s the gist of things: 1. Each installation will have a separate database and separate database user (for security). I set these up manually in MySQL through the command … Read more
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.
I am by no means a mod_rewrite expert but would something like this work? <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / # Force HTTPS for /cart/ RewriteCond %{HTTPS} !=on RewriteCond %{THE_REQUEST} ^[A-Z]+\s/cart [NC] RewriteRule ^(cart) https://%{HTTP_HOST}%{REQUEST_URI} [NC,R=301,L] # Force HTTPS for /my-account/ RewriteCond %{HTTPS} !=on RewriteCond %{THE_REQUEST} ^[A-Z]+\s/my-account [NC] RewriteRule ^(my-account) https://%{HTTP_HOST}%{REQUEST_URI} [NC,R=301,L] # Force HTTPS … Read more
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
GoDaddy is unique among hosts that I’ve seen in that the changes you make to .htaccess files don’t take place immediately. They use some caching system for them in some manner. Turn on the permalinks and wait a day. It’s worked for me in the past when I used to be hosted there.
There is no built-in way to do it. The .htaccess is “printed in the screen” of the wp-admin ones you are setting up the multisite (the same for wp-config.php). That info is never write directly in .htaccess file like the single site. The wordpress core code for multisite / htaccess is here: https://github.com/WordPress/WordPress/blob/703d5bdc8deb17781e9c6d8f0dd7e2c6b6353885/wp-admin/includes/network.php#L543
Your proxy is rewriting everything to index.php, which means that the backend never sees the original URI. The proxy should be transparent, like this: server { listen 80; server_name example.com; location / { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $remote_addr; proxy_set_header Host $host; proxy_pass http://127.0.0.1:8080; } }
Am I missing something simple? You need the L flag (to prevent further processing) and this directive should go at the very top of your existing .htaccess file (ie. before the # BEGIN WordPress section). Unless you have already defined an appropriate RewriteBase directive (the WordPress front-controller usually has this), then you also need to … Read more
Try to add this one function add_rewrite_rules() { $newrules = array(‘^testrewrite/([0-9]+)/?’=> ‘index.php?page_id=$matches[1]’); return $newrules ; } add_filter(‘rewrite_rules_array’, ‘add_rewrite_rules’); Let me know it is working or not.