• Resolved handig

    (@handig)


    Hi,
    I have a WordPress “mapped domains on a subdomain multisite” on WordPress 3.0.4 and want to upgrade to 3.1.2

    I use WordPress MU domain mapping plugin 0.5.2.

    I have some questions on the upgrade.

    I was thinking about doing the upgrade as follow:
    1. backup
    2. update plugins and themes
    3. update WordPress MU domain mapping plugin
    4. Auto upgrade WordPress (I want to auto upgrade as I have several plugins and multiple websites which don’t use the same plugins)

    My questions are:
    a. I read warnings about the automatical upgrade. But according to this post “the problem seems to be caused by a messy previous upgrade in which files are left in a temporary “upgrade” directory with the wp-content directory. In order to solve the problem, you simply need to delete the “upgrade” directory in it’s entirety and then try the upgrade again.” Will this work with upgrading WordPress multisite too? I’m I safe to upgrade WordPress Multisite automatically?
    b. I currently have the domain_mapping.php plugin placed in mu-plugins folder and sunrise.php in wp-content. According to the WordPress MU domain mapping plugin instructions I shouldn’t place domain_mapping.php in mu-plugins. What is wise to do? Can I just try the new version on the plugin in the normal plugins folder? If it not works I just place it back in the mu-plugins folder?

Viewing 10 replies - 1 through 10 (of 10 total)
  • Yes, do the auto upgrade after you make your backups.

    b. no, you’re fine. the instructions were changed so people get upgrade notices for the plugin. You can move it if you wish, but you’re not obligated to. (sunrise.php will stay where it is)

    Thread Starter handig

    (@handig)

    The domain mapping plugin didn’t update automatiscally so I copied the new one over it. This didn’t work but after replacing the old one to the normal plugins folder I could update it (see details here).

    The upgrade went very smoothly.

    Thanks Andrea !

    Thread Starter handig

    (@handig)

    ok, but let’s assume you don’t want the subsite to have the mapping functionality.

    Shouldn’t the plugin do it’s main job at the main site? Mapping/ “routing” the domains ?

    What would break if you only activate it on the mainsite? I tried it and it seems to work, but I’m a little hesitant as the websites on it are in production.

    It has to run on the sub site that you are mapping.

    If it’s active on a site that’s *not* mapped, it’s no biggie… because the plguin check to see if the blog is mapped, sees it’s not, and doesn’t do any more on that site.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    I think handig’s point was that she doesn’t WANT people to see there’s a mapping capability on some subsites… Which is kinda sensible, actually.

    Thread Starter handig

    (@handig)

    I don’t understand it yet. If the mainsite has the domainmapping plugin on it, it just is ‘routing’ the url’s to the subsites. So what’s the use having the plugin on the subsite?

    The domain url goes to the mainsite and this is routing (via the domain mappging plugin) to the subsite. And that is it, or isn’t it?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    The domain url goes to the mainsite and this is routing (via the domain mappging plugin) to the subsite. And that is it, or isn’t it

    That’s it.

    So what’s the use having the plugin on the subsite?

    The subsite is where you say ‘Hey, main domain, I’m also known as seconddomain.com’, AND it’s where you tell WordPress to use ‘seconddomain.com’ instead of maindomain.com/second ??

    Thread Starter handig

    (@handig)

    The subsite is where you say ‘Hey, main domain, I’m also known as seconddomain.com’, AND it’s where you tell WordPress to use ‘seconddomain.com’ instead of maindomain.com/second ??

    Ok, but is that told by the domain mapping plugin on the subsite or does the domain mapping plugin on the mainsite say:

    “Hey, I got this request for seconddomain.com and that is domainid 2, so it should go to the domain created with id 2.”

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    It’s a bit of both.

    The subsite’s the part that also says ‘Hey, WordPress, my alias is seconddomain.com so if someone comes looking for seconddomain.com/wp-admin, that’s me.’

    Thread Starter handig

    (@handig)

    ok, so I conclude that it should be installed network wide.

    Thanks for the clarification.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘How to upgrade WordPress multisite ?’ is closed to new replies.