I've got a blog running - a 1.2 version. I want to upgrade to 1.5.x, but wanted to check it first in a non-public directory. So I created a new directory, with wp-config pointing to the same database that the public blog does. (So they're both on my site, but only one has public links.)
However, despite having all the right files (uploaded from a mirror 1.5x on my machine, where it works), the non-public directory won't show anything. It's just blank. If I kill the wp-config file (renaming it to .bak) I can get to the "create the wp-config" conversation. However, I don't want to go all the way through that in case I break something in the public blog.
Is the problem that the blog only wants to output to a single directory, which is already set? I thought that I could just create new directories which would be able to access the same database; it would just be a new view, moderated through 1.5.x rather than 1.2. Clues?