2 fplanque Jun 17, 2015 04:25

Yes. The thing is that in order to avoid being pestered by people who want to know why their site isn't working - you know, like when you click a button in Word and a page appears - I've fallen into using subdirectories. So I set up a new site on upgrading, and then change the redirect. A private experience, like.
But having tried to utilise multi-domain a few times and never succeeded, I can see what you mean.
So right now I have an install in /015, and I'm doing an install in the root. But because of the 301 redirect I am taken to the old /015 install. I would like to keep the /015 site live while I mess about.
Trying to run 2 instances of b2evolution, one being in a sub directory of the other will create additional problems.
If you want to test you should do it with completely different domains and a separate (temporary) web hosting account. Short of that you are creating your own pain.
Sorry, I should explain: I'm doing this as a preliminary to moving the site to the root.When I get the / site working OK, I'll delete the /015. I wanted to do an update, but to keep it simple for the moment I'll move the /015 site to / by using the backup files, install with the /015 database and convert to utf8, then delete the /015 install. And remove the redirect.
Then try the multi-domain setup where it should be.
@tgodfrey wrote earlier:
Why? Why don't you install b2evolution at the root of your webserver?
That's how it's designed to work and to be hassle free.