Most likely for security reasons or possibly when load balancing traffic across their shared system. I could see how a company like 1and1 could switch IP addresses for shared services. I’m hosting on MediaTemple DV service, which is a static IP. If they dynamically change their IP addresses, then your database is not going to auto update with that new info. If that’s what they said, then that’s true. My second question is – if we DO indeed still need to be using the Trunk version, and given I have already used the ‘official’ / ‘regular’ version that is posted on (makes no sense to my why a specifically un-functioning plugin would be posted to in the first place(?)), what should I do now to back out of what I’ve done, and head down the correct path? Do I need to re-install my WordPress and start from scratch? Or just overwrite the Domain Mapping plugin files with the Trunk FIles and go back through the whole Plugin Install process anew and just re-start that process? So my first question is – do we still need to use the Trunk version of the Domain Mapping plugin? I skipped that and just used the plugin version found at for Domain Mapping because I noticed this Ottopress Domain Mapping Tutorial was made in June 2010, and then Domain Mapping Plugin at had just been updated on and so I thought, well, maybe we no longer need to use the Trunk version since they make no mention of it on the official Domain Mapping Plugin info page at. Log into the site you actually want to map to a new domain, then go to Tools->Domain Mapping.ĭo we still need to be using the Trunk version? The user screen is the simplest way, if you left that option on before. There’s two ways you can actually map a domain to one of your sites. How to do this varies from host to host, but the important thing is that when you visit your new domain (before you do this!) then you want it to go to your main site, as is. Every host is different, and you’ll have to talk to your host to make them able to point the domain name at your existing site. Update: Okay, so there may be more to it than just that, depending on your host. For me, I just give it a new A record with my server IP in it. When you buy a new domain, you will need to edit its DNS settings to actually point to your server IP or CNAME or whatever you do to make the domain connect to your server. There’s a bit of a prerequisite here before you do this. Remote-login is iffy at best, and I want my new domain name to show up everywhere. Generally I leave only the middle two on. You need this enabled for remote login to work. Redirect administration pages to blog’s original domain (remote login disabled if redirect disabled) – This makes all admin pages show up on the original domain instead of on the new domains.User domain mapping page – Turn this on if you want users to be able to put in their own domains for mapping.Permanent redirect (better for your blogger’s pagerank) – This makes your subdomain or subdirectory sites redirect to their domains.The downside is that the URL changes to another domain in order to log in. The benefit of this is that when you log in to one, you log into all of them. Remote Login – This will make your login pages for all sites redirect to your main site to do the actual login.If your server uses more than one, you can enter them all here, separated by commas. The IP address is what most people will want to use. You can either put in the IP address of your server (as defined in your domain’s main A record) or you can put in a CNAME that points to your server. Here you have a few different options, but two main ones that count.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |