Problems installing when site already has content?

  • Resolved msadventures

    (@msadventures)


    20 years, 4 months ago

    I was just wondering if anyone else has noticed this.

    The first time I installed WordPress on one of my websites was on my personal blog site, which was brand new and had no content on it yet. I had absolutely no problems at all installing WP 1.5.2 there.

    Now I’ve been trying to install WP on a different site that I have that has content there already. What I’ve been hoping to do is get WP installed, get the layout done, put the content into WP pages, etc, and then switch over in a matter of minutes, as opposed to having to shut the site down and so forth, but I’ve been having problems trying to get WP installed to that site. I first installed WP 1.5.2, and the first problem I noticed was that I couldn’t get my plugin page to work properly, the plugins wouldn’t activate. I never did get that figured out, but then WP 2.0 came out, so I deleted 1.5.2 and put up a new database and uploaded and installed 2.0, and I’m having problems with that as well.

    Both sites are hosted by the same company….the only difference I noted between the installations on the two different sites was that one site was new and empty, the other site had some content there.

    Has anyone else noticed this? Is it best to install WP on a site when there is no content? Just wondering.

Viewing 9 replies - 1 through 9 (of 9 total)
  • vkaryl

    (@vkaryl)

    20 years, 4 months ago

    I’ve installed wp on a dozen sites with content live. I’ve never had a problem…. Seems odd, but I haven’t any help for you….

    Thread Starter msadventures

    (@msadventures)

    20 years, 4 months ago

    Well, I have yet another site that I’m going to try installing WP on, it’s an old site that I don’t really use for anything and it doesn’t have much content, I thought it would be good to use as a “test” site, so I’ll play with WP over there and see how it goes.

    I was thinking that the content really shouldn’t affect whether WP installs well or not, but it was the only difference that I was able to notice betwen the two installs. Someone more tech-savvy might be able to find more differences, but I’ll go play and see what I can find out.

    Thanks though! 🙂

    vkaryl

    (@vkaryl)

    20 years, 4 months ago

    Hey, report back, okay? Could help someone else…. and keep good records, what you do, what errors you get, etc.

    Thread Starter msadventures

    (@msadventures)

    20 years, 4 months ago

    Will do. 🙂

    citeewurkor

    (@citeewurkor)

    20 years, 4 months ago

    sounds strangely familiar for some reason?

    vkaryl

    (@vkaryl)

    20 years, 4 months ago

    I don’t know that it’s the same sort of situation…. in fact, I think not at all….

    Thread Starter msadventures

    (@msadventures)

    20 years, 4 months ago

    Not really…mine are separate blogs on different sites/servers/IP addresses. Only thing the same is the host, but the websites are completely separate.

    Also, for me, on my second site, the one that already had the content, I wasn’t trying to upgrade to 2.0. I completely deleted 1.5.2 AND the database that was already in place, since I couldn’t get the plugin page to work, anyway. Then I created a new database and uploaded/installed 2.0. But I haven’t been able to get that one running.

    Now, I’ve just installed 1.5.2 on my third website, which is an old site without much content that I’m now using as a “test” site. Instead of installing it in the root directory, like I did with my blogsite, I put it in a subdirectory. I’m having problems with that. When I log in using the wp-login.php page, instead of being taken to the admin panel like I’m supposed to be, I’m shown my directory listing instead, and have to go through the list to get to the page I want.

    Oh boy.

    petit

    (@petit)

    20 years, 4 months ago

    msadventrues: Struggle on!
    Seems like a lot of trouble. My own experience ( lucky me ) is that following the upgrade directives let me upgrade from WP 1.5.2 to 2.0 RC2 and later to WP 2.0 without any problems.
    The blog resides on a UNIX/Apache by my service provider.
    Now the problem with your “old site” indicates to me that the web server doesn’t recognize the index.php file as something to load by default, hence the listing. Web servers by default are configured to recognize index files named index.htm, index.html, default.htm(l) etc.
    If you go to http://<yoursite>/yourblog/wp-admin/ with your browser, the web server should load the index.php page.
    For this to happen the web server must be configured to recognize this page as a valid index page.

    Maybe you well know all this and maybe someone else doesn’t.

    Thread Starter msadventures

    (@msadventures)

    20 years, 4 months ago

    A-ha! That may very well be the issues, I’d completely forgotten about that, I’ll go fix it right now. Thanks for reminding me! D’Oh!

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

The topic ‘Problems installing when site already has content?’ is closed to new replies.