• Resolved hindsight2

    (@hindsight2)


    In 2009, I kept a personal journal in WordPress 2.7.1 on my local machine. My last entry was in Oct-09.

    Last month, MySQL started returning an error: Access violation at address 1000A1F7 in module ‘LIBMYSQL.dll’. Read of address 0000000.

    Not sure what that means, but I have to shut down the MySQL service to keep that error message from poping up every few seconds.

    Now, I’m retiring that old machine and would like to retreive my prior journal entries, but I’m not sure how to go about it. I have a backup file from Oct-09, ending with a .sql.gz extention.

    Would that file contain my WP database and all my journal entries and the uploaded images I used in my entries? If so, how do I get it to be accessable to retrieve the entry content?

    I should mention, when I attempt to log-in to the phpMyAdmin module, I get error #2003, The Server Is Not Responding . . .

    Any help would be much appreciate. I’m not a technical person by nature and find myseld in over my head.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter hindsight2

    (@hindsight2)

    I’m guessing the #2003 error is because I’ve shut down MySQL to avoid the pop-up “Access Violation” error message.

    ???

    Thread Starter hindsight2

    (@hindsight2)

    Oh, one other thing. I don’t necessarily need to restore/fix the WordPress installation on that old machine. Just access the journal entry content.

    I’ll likely not continue keeping my journal in WP on the new machine. I’m leaning toward keeping a series of Word docs, as I once did, given that my spouse and kids are more comfortable with Word than with WordPress.

    When I’m gone, I’d like them to be able to easily access, copy, move, distribute, etc. So, I need to think in terms my ultimate audience.

    All posts and pages will be in that database backup, and you could install WP 2.7 either locally or on a webhost and import that database and recover everything. Your images will be in the uploads folder in wp-content, so save that, too, and put it back in the same place on a new install. Don’t jump to WP3 because the database won’t be upgraded correctly without first upgrading 2.7 to 2.8.5.

    Then you could cut and paste from the page into Word or from the WordPress editor into Word. Or export as XML and import into Word. You can open the database backup with a text editor, but the database formatting will need to be stripped out and the text won’t look like much with no formatting.

    Thread Starter hindsight2

    (@hindsight2)

    Songdogtech — Thank you. That is very helpful. I’ll give it a try right now. I appreciate the head’s-up on the upgrade path. My website is running the 3.0 version; however, I can create a sub-site and install the older 2.7 version to that.

    I’ll report back on how I make out with that.

    Regards,
    -Mike.

    Thread Starter hindsight2

    (@hindsight2)

    I was able to create a sub-domain site and install WP 2.7 without incident. I had some difficulty figuring how to import the backup file from my local machine, but came upon these instructions:

    http://codex.wordpress.org/Restoring_Your_Database_From_Backup
    (good stuff for a relative naive, like me)

    That process seemed to go well, ending with a “Success” message.

    Now, when I click on the wp-posts table in phpMyAdmin, I can see all my posts — So I know they’re there; however, I now get an error when I attempt to access the sub-domain website I created: http 500 Internal Server Error . . .

    Not sure what that means, and I don’t know that it matters. I figured out how to edit entries in phpMyAdmin and I’m able to copy/paste them into a Word doc, so I’m happy!

    Songdogtech, I’m very grateful for your advice! It’s great to have access to these journal entries, again. Thank you very much.

    -Mike.

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

The topic ‘WP on Local Machine’ is closed to new replies.