• Hi

    I have a Multisite production site up and running configured with subdomains, thus installed i the root directory.

    Now i want to test some plugins/themes and more and would like to avoid doing it on the production site.

    I would like to have a secondary install at the same domain (not a local install)

    Can this be done? Taking this in consideration:
    https://codex.www.ads-software.com/Create_A_Network

    WordPress Settings Requirements

    * Giving WordPress its own directory will not work in WordPress 3.0 with multisite enabled. It interferes with the member blog lookup.

    Also, when finished with a development session and the new version is going to be updated on the “live” site. How can this be done in a smooth way?

    Please share your setup enviroments on the hosting side

Viewing 1 replies (of 1 total)
  • * Giving WordPress its own directory will not work in WordPress 3.0 with multisite enabled. It interferes with the member blog lookup.

    this warning has nothing to do with an install running out of a folder and using that folder in the URL. none.

    It clearly states if you’re shuffling the wordpress files in one folder and running the install so it looks like it’s in the root is the issue.

    It is entirely unapplicable in your case.

    Also, when finished with a development session and the new version is going to be updated on the “live” site. How can this be done in a smooth way?

    Please share your setup environments on the hosting side

    I have multiple test installs. If I’m testing a plugin, I install it and play around. If I want to “move” it to a live site, I install it there and set it up how I did on the live site.

Viewing 1 replies (of 1 total)
  • The topic ‘Development/production multisite enviroment?’ is closed to new replies.