• Hey there,
    I apologize first of all because this post is likely to be confusing. I’ll try to be as concise and clear as possible.
    On my domain, sea-glass.org, I’ve set up two directories for MT. One has always been my “test” directory, where I try things out before putting it on my live directory. That test directory is sea-glass.org/wp
    Now, today I decided to upgrade from 1.01 to 1.2. So I followed the upgrading directions and popped everything into my test directory. I noticed that I couldn’t just replace the template files with my old ones, so I started tinkering around, making sure I was only touching design-based things.
    Somehow (and this is where I may lose you) my “blog” (i.e. live) directory got…OVERTAKEN by that test/wp directory. I have no idea how that happened. If you go to sea-glass.org/blog my site shows up fine. But, I cannot login to my blog directory’s wo-login.php. When I log into my test directory’s wp-login.php and post, both http://www.sea-glass.org/wp AND http://www.sea-glass.org/blog show that entry! VERY bizarre. To make matters worse, when a reader clicks on the comments link, it takes them to a post that’s within the wp directory (even though they originated from the blog directory) and if they hit ‘submit’ to comment, there’s an error msg that comments-post.php can’t be found. And it’s clearly looking for that file not in the wp directory NOR the blog directory, but reverting to my root sea-glass.org directory.
    This is just psychotic. Tell me, is my best best reinstalling the whole thing? I have this paranoia not necessarily of losing stuff (I’ve backed up my design files, which matter the most) but of never being able to login to my blog again. Hehe. Any advice at all would be great, and thanks for the help.
    reese

Viewing 7 replies - 1 through 7 (of 7 total)
  • I apologize first of all because this post is likely to be confusing. I’ll try to be as concise and clear as possible.
    On my domain, sea-glass.org, I’ve set up two directories for MT.

    Yep, I’m confused… 😛
    What have you set up in your options for the WordPress URI and the blog address URI?

    Thread Starter reese

    (@reese)

    Hey, sorry to confuse 🙂
    First, to summarize:
    my domain is sea-glass.org
    my BLOG is located at sea-glass.org/blog
    my TEST mt directory is sea-glass.org/wp
    I use that test directory before I put it in the blog directory. But now it’s like the test/wp directory has taken over 😉
    I can ONLY access my options within the sea-glass.org/wp directory, and the URI in that for both WordPress and blog address say: sea-glass.org/wp
    Now, if I could get into the options/admin/whatever for my sea-glass.org/blog directory, I’d be able to see the URI settings for that, but I can’t. Won’t let me login to that anymore, but if I login to sea-glass.org/wp and post something, it shows UP on sea-glass.org/blog.
    Make sense now?
    I know, I’m confused, too.

    When you did your second install, did you give the tables a unique prefix? This is how you can have multiple installs using the same database. You might have wp_ for the prefix of one install, and test_ for the prefix for the other install, for example.
    If you did not change the prefix, and installed both instances of WP into the same database, then you over-wrote the first install with the second install, which means that in reality, you have only one install-that being the second one.
    Does that help at all, or am I shooting in the dark?

    Thread Starter reese

    (@reese)

    to clarify a bit further: both directories (wp AND blog) have their own installation of MT in them.
    WHen I upgraded, I upgraded ONLY to my wp directory. The “blog” directory had the old version of wordpress still in it. I can see where, me naming that other directory wp, probably threw you off. ANyway, there’s wordpress in both directories, but it seems the one named wp is hungry or something.

    Thread Starter reese

    (@reese)

    that helps. It sounds like you are saying that the DATABASE doesn’t care that I have two separate directories with two different wp installatiosn in them. Because when I upgraded, it upgraded the database, and the OLD version of WP, which is in the blog directory, went to the database and got confused.
    That sounds to me like what you are saying. Is that correct?
    If it is, I think what I will do is also ‘install’ to the blog directory with that hopes that it will fix this. Or i could remove everything completely (including the databases) and just install the latest version from scratch. what do you recommend?
    and thank you for your help 🙂

    @reese, you keep mentioning MT which to most people on these forums means MovableType. So I’m guessing you’re a somewhat recent convert from MT to WordPress (WP). One of the big differences between MT & WP is that MT generates a bunch of HTML files for all your posts when you enter the posts but WP justs adds your post to a MySQL database and then generates the pages for the post whenever somebody comes to your site to look at them.
    The MySQL database is not stored as a file in your web directory but is elsewhere on the webserver. So when you install WP; you create a wp-config.php file that tells WP how to connect to that database. If that wp-config.php file is exactly the same in both sea-glass.org/blog and sea-glass.org/wp then both installations are connecting to the same database and that’s why you’re having problems.
    If you want to run 2 installs of WP on the same server; then you’ll need either to have 2 databases or to alter the following line in one of your wp-config.php files:
    $table_prefix = 'wp_';

    Thread Starter reese

    (@reese)

    hey manzabar,
    First, sorry for the MT references. That was complete stupid typing on my part. I meant WP. :/
    Someone helped me out a lot with this, so I got it resolved…thank you for help with it, though!

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘national upgrading disaster’ is closed to new replies.