WordPress.org

Support

Support » Multisite » Moving multi site to Xampp

Moving multi site to Xampp

  • In unsuccessfully tried to copy my site to a new URL, coudn’t get past the user permission problem when importing the db.

    So I reluctantly installed XAMPP and I finally got the db imported, but I get a 404 when trying to access the site.

    I did the URL replacement before importing and here’s my htaccess:

    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]

    # uploaded files
    RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

    # add a trailing slash to /wp-admin
    RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule ^ – [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
    RewriteRule . index.php [L]

    And the relevant part of the config:

    /** The Database Collate type. Don’t change this if in doubt. */
    define(‘DB_COLLATE’, ”);
    define(‘VHOST’, ‘no’);
    $base = ‘/’;
    define(‘DOMAIN_CURRENT_SITE’, ‘http://127.0.0.1/wordpress/’ );
    define(‘PATH_CURRENT_SITE’, ‘/’ );
    define(‘SITE_ID_CURRENT_SITE’, 1);
    define(‘BLOGID_CURRENT_SITE’, ‘1’ );

    I’ve been trying to follow http://codex.wordpress.org/Test_Driving_WordPress#Installing_an_Existing_WordPress_Site

    Go to C:\apachefriends\apache\conf and open the file called httpd.conf in a text editor.
    # About line 166 you will find: #LoadModule rewrite_module modules/mod_rewrite.so.
    # Remove the # and save the file (this switches mod_rewrite on).

    I couldn’t find it at first and then realized that the file had no “”#”

    LoadModule rewrite_module modules/mod_rewrite.so

    So I left that alone. Was I supposed to do something?

    Upgrading to 3.0 was hell because the official upgrade doc was missing some steps for MU and I’m wondering what I’m missing now.

    Appreciate any pointers!

Viewing 15 replies - 1 through 15 (of 16 total)
  • From http://codex.wordpress.org/Create_A_Network

    # Giving WordPress its own directory will not work in WordPress 3.0 with multisite enabled. It interferes with the member blog lookup.
    # You cannot create a network in the following cases:

    * “WordPress address (URL)” is different from “Site address (URL)”.

    From http://codex.wordpress.org/Test_Driving_WordPress#Installing_an_Existing_WordPress_Site

    If everything so far has gone well, it is now time to visit your blog! In your browser, type in http://127.0.0.1/wordpress/index.php or the actual name of the folder you created for your WordPress files.

    So I can only have ONE test site and it has to be in root?

    I did move it and imported the db for about the 15th time:

    Oops! Firefox could not find http

    Moderator James Huff

    @macmanx

    Support Team Rep.

    I haven’t used multisite yet, but from what I recall from all the topics I see here every day, you can only have one multisite network per domain.

    Now, if you weren’t using multisite, you could install WordPress in any directory or sub-domain that you wanted to.

    Thanks. So is there anybody who can tell me how to get just one installation on xampp working?

    I know the index.php and index.html are there, the xampp directory works and I had a new wp install running fine before I moved my existing installation.

    Moderator Andrea Rennick

    @andrea_r

    It *could* be because you’re using an IP address.

    also:

    Upgrading to 3.0 was hell because the official upgrade doc was missing some steps for MU and I’m wondering what I’m missing now.

    Which docs? Because I know Upgrading WPMU was updated.

    Hi Andrea, that’s not the doc I read when I upgraded, I just followed the instructions with the upgrade and it didn’t mention anything special for MU.

    I really didn’t want to upgrade because and waited until the day BEFORE the 3.01 release — go figure. Fortunately the 3.01 upgrade was the usual 2-minute install.

    Regarding xampp, I just changed the db and config to http://localhost/ and keep getting the:

    Oops! Firefox could not find http

    I’m giving up. I’m so worn out, I actually just crashed my main site, changing the config there, and that’s of course what I was trying to avoid. 55 windows open and haven’t gotten any “real” work done in over a week.

    Earlier I posted at my “fun” site at http://trado.info/permaculture/2010/08/10/no-more-tilling-dont-kill-your-earth-worms-insects-fungi-bacteria-nematodes/ and noticed that the code to embed Amazon code is stripped after every edit. Reinstalled unfiltered MU, the problem doesn’t go away. This never happened before the upgrade.

    The one thing I’d really like to do now is import all my blogs and settings to a new multisite install and this way ELIMINATE all MU related problems — which I’m sure there will be more and more due to the difference in structure.

    Has anyone tried that?

    Moderator Andrea Rennick

    @andrea_r

    The one thing I’d really like to do now is import all my blogs and settings to a new multisite install and this way ELIMINATE all MU related problems — which I’m sure there will be more and more due to the difference in structure.

    But the multisite feature is what was MU. And very little was changed – it acts the same.

    I also covered the upgrade from MU to 3.0 over at my blog.

    and noticed that the code to embed Amazon code is stripped after every edit. Reinstalled unfiltered MU, the problem doesn’t go away. This never happened before the upgrade.

    Are you pasting that code in while logged in as the super admin?

    Yes. Does it only work for super admins?

    And from what I read the config and htaccess differ for NEW multisites from the old MU installs and the multisite I had installed on xampp worked fine, can’t get my upgraded MU install working for anything. So there MUST be something different.

    Also noticed that I still have my MU plugin directory.

    I see LOTS of problems in the futures because all the instructions are for multisite, NOT for MU upgrades. I really wish the MU forum had remained open for people who used MU.

    Moderator Andrea Rennick

    @andrea_r

    Yes. Does it only work for super admins?

    Yep.

    And from what I read the config and htaccess differ for NEW multisites from the old MU installs and the multisite I had installed on xampp worked fine, can’t get my upgraded MU install working for anything. So there MUST be something different.

    They are, but internally, wordpress can tell if you’re an upgraded MU install verses a post 3.0 one.

    Also noticed that I still have my MU plugin directory.

    Because it’s still used.

    I see LOTS of problems in the futures because all the instructions are for multisite, NOT for MU upgrades. I really wish the MU forum had remained open for people who used MU.

    the old fourms are redirected here. Most of the frequent posters from there – including myself – had notice and moved over accordingly. At some point the posts may follow. But this is now the new forum for mu questions as well. The old forums are still searchable via google.

    There *are* instructions for mu upgrades.
    http://wpmututorials.com/how-to/upgrading-from-wpmu-to-wp-3-0/

    And MU did not support the use of just http://localhost/. Long and well-known issue.

    And MU did not support the use of just http://localhost/. Long and well-known issue.

    So is THAT why it doesn’t work?

    If so, I definitely need a clean multisite install.

    Moderator Andrea Rennick

    @andrea_r

    Probably, if you put mu on localhost, then yes.

    I installed a new multisite on xampp and it works fine. I even started to import some of my about 30 blogs.

    But it’s so much work, and then I haven’t found any instructions on how to get it all back on the live site, I’ve given up on a test site.

    I really wish that the WP instructions contained some warnings for MU users to avoid all these giant wastes of time.

    Moderator Andrea Rennick

    @andrea_r

    Yes, it’s work. Running a network has always been work and required a higher level of knowledge. It’s up for you to decide if you want to learn it or not.

    The warning are in some of the docs, in the help text (right in the backend) in the codex where it explains procedures, here in the forums and in my blog.

    Dear, Andrea, so could You please help by giving the links to the Documentation that talk about moving a mature multisite WordPress installation to a new domain.

    With all the plugins, databases, file uploads remaining the same, if possible.

    Thank You very much!

    Moderator Andrea Rennick

    @andrea_r

    robertjakobson

    @robertjakobson

    I do not think You quite understood me clearly enough,

    what I am looking to accomplish is to move a fully mature multisite with two blogs to a brand new WordPress installation in another domain.

    Are the procedures still the same?

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘Moving multi site to Xampp’ is closed to new replies.