wordpress 3 network (multisite) on a local development site

  • ResolvedModerator keesiemeijer

    (@keesiemeijer)


    14 years, 5 months ago

    Hello I’m testing wordpress 3.0 and it looks really good. But I have trouble implementing the new Network (multisite) feature. I used Mamp and Headdress (Mac) to create the local site. This produces url’s like these: https://localhost:9016/ When I try to make a “Network” I get the following error: “Error: You cannot install a network of sites with your server address. You cannot use port numbers such as :9016.” What local address does work? Or is a network on a local site not possible right now? I would really like this feature for multilingual sites but I need the ability to develop local.

Viewing 15 replies - 31 through 45 (of 52 total)

  • Thanks, Andrea. Searched the full DB and replaced all instances, but I’m still not able to get this running. Set up a virtualhost this morning and if I drop an index.html file in the directory, it opens fine. Once I use index.php though things get wonky. Table prefixes I think are the problem. If I look at the DB in phpmyadmin, I have the following prefixes:
    wp_
    wp_1_
    wp_2_
    wp_3_

    When I use ‘wp_’ as the table prefix value in wpconfig, I get “Error establishing a database connection.” If I use wp_1 as the prefix in wpconfig, I get to the site’s 404 page with some plugin errors at the top. Trying to login to the WP backend doesn’t work because usernames and passwords aren’t being found, and the lost password functionality doesn’t work either, it simply returns the email doesn’t exist message. I’ve looked in all of the user tables and the username and email are in all of them.

    Any thoughts or help greatly appreciated.

    wp_
    wp_1_

    It’s the presence of both of these that is confusing WP. One means it;s a single WP install that had the network enabled. (wp_) the other one (wp_1_ ) means it was an upgraded wpmu install.

    which was it?

    It’s an updated wpmu site. It’s running live right now with no issues, and I’ve looked at wpconfig on the live site, and that’s using wp_ as a prefix, so I’m pretty confused…Thanks for the guidance.

    Specify in “wp_” as the db prefix is *fine*.

    It’s just in an upgraded mu install, you should *not* have wp_posts etc… tables. They should be wp_1_posts for the main blog.

    Did you rename them?

    I didn’t rename them, but I didn’t do the upgrade. When the upgrade occurred the site was also moved to a different server, same domain. Needless to say I’m not sure what the guy did who moved the site and upgraded it, I’m coming in a bit late on this project. I just tried renaming the wp_ prefixes to wp_1_ and went through the process for doing this found in the codex, but still no luck. Just get the 404 page, no links working, and no ability to login to the backend.

    Hi,
    Any change someone can write up a quick guide on how to install wp3 multi site on localhost (using xampp)?

    I read throw the whole thread an got a bit lost ??

    THANKS ??

    Hi,
    like shmar77 you got me lost. What about a nice and clear tutorial? Anyone ?

    if my main domain is localhost/wp_multi/
    and my subdomain is localhost/wp_multi/dev what should i do ?

    Thanks

    You can’t use wildcard subdomain on localhost for starters.

    Follow any tutorial out there for installing just wordpress locally. then create the network and use SUBFOLDERS.

    So Andrea,

    My situation is that I’ve got a WordPress 3.0.1 installed at a hosting company (Dreamhost.com) with subdomain multiuser enabled, with buddypress running. You can see the site here: https://jobs.localjobs.com

    I want to establish a local host testing environment – what option do you think is the best – given that you said the subdomain approach won’t work on local host testing environment:

    1. I’ve created a fresh local install of WordPress (I’m running Mac with OS X (latest version) and I”m using MAMP. Should I try to now configure this as a multi-user locally and then import my live site data via the EXPORT/IMPORT WP approach to populate a local database.

    2. Other….????

    Wildcard subdomains won’t work locally… but you can put in individual subdomain records. ??

    Yes, do #1. also put in your local address in the db with a search & replace.

    Is it important that ‘multiuser’ be enabled on WP ….BEFORE…..we attempt the file mods changes noted in this thread, or not? I went ahead and did it, but didn’t enable WP for multiuser yet…..doooopsss..

    You do not have to do any changes for multisite to work locally.

    (this is the hazard with posting about your particular issue in an ongoign theread – things get muddied)

    So does using subdomains on localhost work or not?

    Wild card subdomains don’t, what if I don’t use wildcards but set up specific subdomains? And how do I do that?

    I need to make sure the site I’m building works properly locally before updating it, with subdomains.

    So does using subdomains on localhost work or not?

    Not wildcards.

    Yes, you can set up subdomains manually. Set them us by making one in the hosts file the same way you do fake domains. Or a serveralis in your local apache.

    Thanks for clearing that up Andrea_r. XD

    I’ve got the subdomains set up in apache and they’re working fine. Is there anything specific I have to do in WP (apart from the obvious)?

    eg. The dl zip has WP in its own directory. Do I copy that dir straight into my root or does that count as having WP in its own dir with regards to setting up a network with subdomains (ie it won’t work). In which case should I ignore the top level ‘wordpress’ dir in the zip and just copy everything inside it straight to my root?

Viewing 15 replies - 31 through 45 (of 52 total)
  • The topic ‘wordpress 3 network (multisite) on a local development site’ is closed to new replies.