Support » Fixing WordPress » Don't Laugh But…need help…

  • Yikes, this was my very first WP blog:

    It’s sooooo old it is no longer supported in any browser. I can not look at any of the posts. There is a lot of great content, including podcasts, that I want to be searchable. There were many contributors to that blog as well who use it as a calling card to get writing gigs. I have been woefully lax in updating/migrating the content to the latest WP version.

    Problem is I don’t know how to (with this version) to back up the database so i can then import the file to the latest version which I realize I will have to manual install.

    Perhaps, DL latest wp version to a separate folder…but how to get content from this blog to load into new?

    Advice, ideas, anyone have to do this recently and know what should be done? Willing to share knowledge?

Viewing 15 replies - 1 through 15 (of 31 total)
  • Moderator Mark Ratledge


    Forum Moderator

    The blog page source says that’s WordPress 2.0.5, so what you need to do is, yes, backup the database. You’re at GoDaddy, so you can backup the database in your hosting control panel or use a backup plugin.

    And then do a incremental WordPress upgrade so things get updated in the right sequence. You need to go to 2.1, then 2.1 to 2.3, 2.3 to 2.5, 2.5 to 2.8.5, 2.8.5 to 3.0

    That’s a lot of work, but if you want to save the content and not start from scratch, it needs to be done that way. Old versions are at

    I doubt your theme will work very well afterward, so you’ll need to change themes and add your header image to it.

    Your blog is integrated into the main naica static site, so be careful.

    Your blog is integrated into the main naica static site, so be careful.

    I wasn’t the one who installed this blog many moons ago but merely managed the content. However, I’ve done a number of WP blogs for myself and others.

    What exactly do you mean? As far as I see she installed into a WP folder in the main root folder for the naica domain. Can I not just leave it there installing upgrades into that subfolder?

    And exactly how does that work? The incremental upgrades? Because in the last few years I’ve been using WP on my own I just auto upgrade (backing up my database and saving copies of css template files before doing so) through the dashboard.

    I’m a little leery now but needs to be done as many of the contributing writers have complained about using the link on resumes and cvs only to be told by potential employers they can’t see the content.

    Thanks for input and i am also reading through the codex files as well to see what needs to be done.

    Moderator Mark Ratledge


    Forum Moderator

    From this end, there are static html files in root, but the blog is in /wordpress/, so WP could be installed in root and configured to be at /wordpress/.

    You have to do manual upgrades, because you can’t configure automatic upgrades for any version than the current. Upgrading WordPress « WordPress Codex. And not overwrite any static files for the non-WP site, which shouldn’t be a problem as WP doesn’t have any .html files. But still, backup the non-WP files.

    Interesting. Spoke with GoDaddy.
    Their suggestion after backing up the old database files for WP 2.0.5 was to create a new directory with a different name (instead of the ‘wordpress’ folder we have in root directory, auto install WP 3.0 into that directory, and then do their restore files directing them to the new folder with 3.0.

    The older version operated under php4.0 not php5…he said it wouldn’t matter. He did say we’d have to import image content from old folder but at least all the plugins (now outdated anyway) and post text files will be there which to me is of paramount importance! I have all that visual and mp3s in folders on my server. I can re-import on a post by post basis.

    But I wonder if this is going to work?

    if you follow the godaddy advice – you will break your database as there have been many changes since 2.0.5

    songdogtech gave you perfect instructions to come out of this problem free

    Hmm, Godaddy made it seem too easy. It never is, is it? 🙂

    But still, backup the non-WP files.

    That would take FOREVER.
    I don’t see the issue if the blog files reside in their own folder with their own database?

    that may be over-cautious
    if it’s dear to you, though…

    Well, I started the manual upgrade using the info from the Codex page. It inferred that I copy over the old files inlcuding my wp-config.php..I did so.
    Now I am getting this:

    Warning: require(/home/content/N/a/i/Naica2005/html/wordpress/wp-config.php) [function.require]: failed to open stream: No such file or directory in /home/content/N/a/i/Naica2005/html/wordpress/wp-login.php on line 2

    Fatal error: require() [function.require]: Failed opening required ‘/home/content/N/a/i/Naica2005/html/wordpress/wp-config.php’ (include_path=’.:/usr/local/php5/lib/php’) in /home/content/N/a/i/Naica2005/html/wordpress/wp-login.php on line 2

    When I went back to look at files through FTP I only have the wp-config-sample.php file. My old wp-config file is gone!

    I vaguely remember you’re supposed to do something with that sample file….?

    Well, I’m screwed. I copied over the old wp-config.php file based on this from short instructions Codex page:

    NOTE – you should replace all the old WordPress files with the new ones, including those in the root directory like index.php, wp-login.php and so on. Simply copying the contents of the zip you downloaded over the top of your existing files should achieve this. Make sure you copy all the sub-directories as well. Don’t worry – your wp-config.php will be safe.

    But when I clicked the extended instructions it said not to…sometimes I really hate WP Codex instructions!

    Now what? The database is all backed and the file is secure through Godaddy. Can I use it to reinstall the old version?

    Well, I configured the wp-config folder and it does take me to the wp-admin/login page. However the username and password i always used for the 2.0.5 version is not working.
    Which file can i manipulate to assign a new username and password that will work?

    Okay, well the videoplayer is there and so is the old banner and sidebar: None of the posts are there..obviously I have to import the backed up database.

    I have a question:
    1. Can I just start plowing through the WP versions, replacing necessary files (this time I WON’t override the wp-congif.php file), keeping the wp-contents folder with old theme and plugins but NOT import the old database each time?

    Meaning can I do that at the last upgrade 3.0? Or should I also just import the old database when I upgrade to each new version?

    And if I have to do that then how do I do that? Where do i go to do that, restore old DB?

    Moderator Mark Ratledge


    Forum Moderator

    Don’t worry – your wp-config.php will be safe….

    That’s because there is no wp-config.php in the download package. If there was, it would overwrite your existing wp-config.php file. There is only a wp-config-sample.php. So you must have deleted your wp-config.php to begin with.

    Did you *install* that newer version of wordpress or did you *upgrade* it? If you installed it, then that’s why your old posts are gone. If you upgraded it, then your posts would be there.

    You have to upgrade each version by going to each time. That’s what I said hours ago: the database has to be upgraded each time.

    Resetting Your Password « WordPress Codex

    I followed the directions from this link you provided:
    Upgrading WordPress « WordPress Codex.

    Honestly, now I’m not sure what I did. You didn’t provided that last url the first time. So I assumed by following the directions via the “Upgrading Wp” on the codex page would work but it sounds like what I did was install 2.1 instead of ‘upgrade”

    So even though I backed up the database for the 2.0.5 version all the posts are gone? I can’t just import them into the latest version I have (now 2.1)?

    Obviously I confused the info provided on the Codex page?

    Moderator Mark Ratledge


    Forum Moderator

    I don’t know what you did; you did misread the codex. But if you have a database backup, then your posts are not lost. You need to import the database backup with phpmyadmin and then go back to upgrading: Restoring Your Database From Backup « WordPress Codex. Or ask GoDaddy to roll back the site to their backup. Sometimes they can do that.

Viewing 15 replies - 1 through 15 (of 31 total)
  • The topic ‘Don't Laugh But…need help…’ is closed to new replies.