WordPress.org

Support

Support » Alpha/Beta » WordPress 3.0 and Domain Mapping

WordPress 3.0 and Domain Mapping

Viewing 15 replies - 1 through 15 (of 31 total)
  • I’m eagerly waiting for this answer too 🙂

    I wrote how to use it here:
    http://wpwebhost.com/using-multiple-domains-with-wordpress-mu/

    (if it says it won’t work with subfolder blogs, ignore that part. It does now. 🙂 )

    The short version is: you have to log in to the backend of the blog you want to map a domain to. then look under the “Tools” menu.

    this plugin works better and is automatically run on all blogs if you put the file in the mu-plugins folder.

    Floyd-out
    Member

    @floyd-out

    Thanks a lot Andrea, this works now !

    Do you how I could add a www subdomain to all domains mapped ?

    It keeps on redirecting me to http://blog2.com and I want a http://www.blog2.com address !

    Thanks !

    CHeck to make sure your server’s not stripping it out and you’ve put the www in there when you mapped it.

    I know mu used to strip out the www, but 3.0 doesn’t. I haven’t fully tested that part yet, so take good notes. 😉

    Thanks, Andrea!

    The article is also valid to WordPress 3.0 ou just WordPress MU? 🙂

    Same process, yes. Mostly because the bulk of the setup is on the server side & with DNS records.

    W.r.t WPMU, I find that there are two plugins:

    1) domain mapping, (ref: above)
    http://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/

    and another one goes by the name:
    2) multisite manager
    http://www.jerseyconnect.net/development/multisite-faq/.

    Do they perform the same function?

    thanks

    No, they do not.

    multi-site is a term originally used on wordPress MU for a different purpose. Note the second plugin has also not been updated for some time.

    I’m in the process of migrating a dozen sites or so to a single WP 3.0 site, using domain mapping. There seems to be some sort of javascript error, on account of plugins calling siteurl to define paths to the js files. It appears that the domain mapping plugin _is_ performing some checks on whether siteurl is called… but that doesn’t seem to be working for me.

    So, my solution was to go into the database and redefine siteurl for the problem site to the same as the mapped domain. Things run smooth after that. But, is that the right way to go about doing it?

    <aside>If only I’d known I could have done it with a subfolder structure… would make my work a wee bit easier.</aside>

    Sure, if it works. Also if you want to hide the originating subdomain.

    Dang, does the plugin say it only works on subfolder installs?

    Thanks… that puts my mind at ease.
    More than hiding the subdomain, it was necessary because of the cross-domain javascript problem. It works fine, so far… have only tested it on one domain so far, and if this works smooth, I’ll probably do it on all the others.

    I hadn’t read the changelog when I installed it. I just remembered it from when I last tried it out, and at that time only subdomains were supported.

    Thanks, once again.

    Yep, there’s a for-pay domain mapping plugin that swaps out all subdomain references when you map a domain. Works dandy.

    and of course, you can manually change those values.

    bhadresh08
    Member

    @bhadresh08

    I am using WordPress MU 2.9.2 with domain mapping plugiin.
    but i am facing www striping problem. Can any one know that how i can solve it?

    If Domain Mapping now works for sub-directories, is there any reason to setup 3.0 with sub-domains? It might be a preference for some people, but are there intrinsic advantages for people running distinct sites with unique web addresses?

    Choosing subdomains or sub-directories is a big decision to make, and a bigger one to un-make. I can’t find a compelling reason to choose one or the other.

    @andrea

    Do you have a url for that pay-to-use domain mapping plugin that swaps out the subdomain references?

    Thanks!

Viewing 15 replies - 1 through 15 (of 31 total)
  • The topic ‘WordPress 3.0 and Domain Mapping’ is closed to new replies.