WordPress.org

1. Catherine_B
   Member
   Posted 3 years ago #

   Greetings, All -

   I have spent 7+ hours and am further behind than when I began this today! I need help, please. Facts:

   1) Had a 2.1 blog on the root directory of godaddy acct installed - wp blog files NOT installed through their control panel in 2007.

   1a) G/D does not show the WP 2.1 through their convenient, easy-to-upgrade control panel as I ftp'd the original another way (don't even remember the details). However, of course tech support could go into my hosting account and see the wp files, although it didn't help anything.

   2) Wanted to upgrade to 2.7 through the godaddy control panel (easy) but did not want to overwrite root files.

   3) Backed up the db file as client is changing the theme anyway, so figured that would not matter.

   4) G/D suggested download 2.7 into a subdirectory to test it, restore the backup into the test subdirectory to make sure it works, then if it works, delete the test subdirectory (through the control panel) and feel confident that I could download 2.7 (through the panel), let it overwrite the 2.1 version on the server now, and then simply backup the database file with all the posts and text.

   5) So I did this. First, the default plain blog skin came up at: [domainname.com}/testblog. So 'restored' the db to that blog. Didn't work.

   6) So removed 2.7 in the subdirectory properly through the panel, thinking I would get back to square one. Typing in the original blog name, get this WordPress error page message:

   "Error establishing a database connection. This either means that the username and password information in your wp-config.php file is incorrect or we can't contact the database server at mysql245.secureserver.net. This could mean your host's database server is down."

   7) Called G/D and they tested the db and it works. Cannot/will not give me WordPress support, suggested online help.

   8) All original blog files dated 04/01/07, including index.php and wp-config.php, appear as always in the dotcom root. Also have the db file downloaded onto my hard drive (before any backups were attempted, so theoretically 'pure') plus 2 saved versions on the G/D server. I have also copied an identical 04/01/07 directory into another folder on the G/D server for safekeeping.

   *Here's what I want and need, 'please' - as my client is without his blog and very worried about his work (as am I!):

   9) I want to download 2.7 through the G/D panel into the root dotcom where the 2.1 version is, which would overwrite the 2.1 version.

   10) I want to restore that big db file.

   10a) The theme is irrelevant as he's changing it; so the default would be fine.

   10b) I know 'something' about the wp-config.php file as I poked around in it today and saw the database number, username & pw, etc. I also - in the 2.7 documentation - noticed that there are some new strings (security keys) added in 2.7, so I may easily be confused if I have to modify the original wp-config file to make the database work with the new 2.7 version.

   10c) I was unable to access the my admin php database file (for the original database file) and the username and password wouldn't let me in, although I used the same username (which was the database file id number) and password from the wp-config file! Huh??

   11) G/D doesn't have an 800 number, and I've spent 90 mins long distance today and gotten in worse trouble, so that's not much of an option.

   I'm STUCK! I need help badly.

   With thanks and appreciation from Catherine

2. figaro
   Member
   Posted 3 years ago #

   Catherine,

   It sounds like you have had a long and frustrating day. As long as you have the database backed-up (which is sounds like you do) and your uploads directory from the original wp-content directory, then you will be able to recover.

   Trying to go straight from 2.1 to 2.7 is not a good idea. I would suggest going to 2.5.1 first. Then go to 2.6.5, and then to 2.7. You will need to change the config.php file when you get to 2.7.

   There are a couple of videos at the link below on upgrading using Cpanel...Godaddy doesn't have Cpanel, but their control panel is pretty good and works very similar. Take a look and if you can't figure it out, drop me an email and I'll give you a hand.

   http://educhalk.org/blog/?p=17

3. Catherine_B
   Member
   Posted 3 years ago #

   Hi Figaro -

   Thanks so much for stepping in. I won't be able to upgrade to 2.5 via G/D's panel; their only wp upgrade option is the 2.7. So I'd have to do it externally through dreamweaver or another ftp method.

   *Is there just a way to scrap the 2.1, go directly to a 2.7 fresh new download, then import/backup/restore the original single db file to the new 2.7?

   With appreciation from Catherine.

4. figaro
   Member
   Posted 3 years ago #

   I won't be able to upgrade to 2.5 via G/D's panel; their only wp upgrade option is the 2.7.

   Sure you can...watch the videos. They may only have 2.7, but you can get all the prior source code here:

   http://wordpress.org/download/release-archive/

   You upload your own source code to do the upgrade...you don't need to do it through Godaddy's auto-installer.

5. Catherine_B
   Member
   Posted 3 years ago #

   Figaro, May I please ask:

   Does it make sense to you that the unsuccessful install of 2.7 has messed up the original site altogether where it won't display on a browser and gives that database connection error?

   Is it necessary to go through uploading several versions, or can I simply put in a new fresh 2.7 and then use the 2.1 database file to restore the posts from? (The former theme is irrelevant.)

6. Catherine_B
   Member
   Posted 3 years ago #

   In the meantime, I have gone to the helpful links you provided. If I cannot bypass all of that and overwrite with a new fresh 2.7, is any of those three file types better to use? I wonder if I can unzip a file on the server? I haven't tried that before.

7. whooami
   Member
   Posted 3 years ago #

   Is it necessary to go through uploading several versions, or can I simply put in a new fresh 2.7 and then use the 2.1 database file to restore the posts from? (The former theme is irrelevant.)

   its not necessary, but it is reccomended by those of us that have done hundreds of upgrades, **successfully**.

   You cannot import tables from 2.1 into a 2.7 database -- thats not an option.

8. Catherine_B
   Member
   Posted 3 years ago #

   <<You cannot import tables from 2.1 into a 2.7 database -- thats not an option. >>

   NOT the answer I wanted!!

   Well, I wish I knew why the old site won't come up any more. Then I could at least do this tomorrow when I'm fresh, but I'm worried about that database file, even though its file size remains the original so it 'looks' like it's there.

   {{I'm a designer and outta my league on this kind of stuff}}

9. whooami
   Member
   Posted 3 years ago #

   what you need to do, is put back 2.1 - fix that, so its working.

   and go from there.

10. Catherine_B
    Member
    Posted 3 years ago #

    Ah - You just answered the question in my mind, Whooami. Wondering how upgrading would work if the current version doesn't work.

11. whooami
    Member
    Posted 3 years ago #

    youre not going about this right, and by right, i mean logically.

    you cannot upgrade a broke site into working. thats not how it works.

    UNLESS, you get very lucky.

    you need to fix whats there -- take care of that problem, and then move onto upgrading.

    And I mean this in the kindest way -- if you dont know wordpress, you shouldnt take jobs that involve it, until you do get it -- or have at least gained some mastery in how to troubleshoot it. I can upgrade a 2.1 install to 2.7 in about 30 mins (doing all the incremental upgrades), and most of that time is spent unpacking zip files. But that didnt happen overnight, just like everything else, there's an attached learning curve.

12. Catherine_B
    Member
    Posted 3 years ago #

    Right - That's what I'm going to do, try to fix the 2.1 first.

    I put the original one up without a hitch and another two as well. Sometimes people don't know 'what they don't know' until they do it wrong. Color me that.

    Don't forget - I did exactly what the G/D tech guy (who meant well) suggested and got messed up: download the 2.7.

13. Catherine_B
    Member
    Posted 3 years ago #

    OK ... 2.1 is back up and working after 13-1/2 hours {{whew}}.

    The fixes were NOT THAT HARD. Just a nugget or two of information if godaddy had been willing to be just a teeny tiny bit helpful instead of refusing to have anything to do with wordpress (beyond facilitating the downloads from their site) ... would have saved an entire day.

    One of the problems was the password inside the config file did not work; it would not allow access the php admin file - and therefore that same config file was apparently 'never' going to work to pull the proper database file. When I finally put together that there might be a connection and changed the password (which then allowed access to the php admin area) - and then plugged the new password into the config file, voila! Back in business.

    I'm sure 'now' that all that time copying and duplicating the 'first' 2.1 set of files was unnecessary; the problem from many hours ago was apparently that password that wasn't working; therefore the simplest repair/restore actions hit a brick wall every time.

    SO: Apparently the advice now is to go: 2.5.1, then 2.6.5, THEN 2.7. I'll pick back up tomorrow on it.

    Thank you.

14. whooami
    Member
    Posted 3 years ago #

    for what its worth, the changes from 2.3 to 2.5 were significant, and historically, are where the issues with missing comment counts, etc.. happen, in MY experience.

    If youre trying to skip versions, 2.3.3 might not be one you want to include.

    You can make it all much faster, and alleviate a great deal of pain by NOT uploading the wp-includes/js directory and all its subdirs, until the very end (that directory serves no purpose in the upgrading process).

    Lastly, PLEASE make sure that you delete ALL of the old core files before uploading new ones, and make the changes to wp-config.php as you go -- I could explain why, but it would take a book. :P Just trust me on all of that.

15. Catherine_B
    Member
    Posted 3 years ago #

    Whoo -

    Thank you! Your post came in the nick of time, because I was 'just about' ready to pull the plug and do the 2.5.1, which is downloaded, unzipped, and sitting on the server. I have duplicated the entire 2.1 files. Now I'll get the 2.3.3 and do that next. You did not say to skip any others, so I guess you think: then go 2.5.1, 2.6.5, then 2.7.

    Right, I knew to check the config file and make sure the blog still operates after each upgrade. Love that, that I can leave off the wp-includes/js directory until I get to 2.7.

    So I'm going to go in and deactivate plugins, tuck the original files into a new folder on the server (for deletion later), leave the includes/js files, then 'move out' the upgraded files from their own folder on the server to the root.

    I am trying to follow the upgrade instructions here:

    http://codex.wordpress.org/Upgrading_WordPress_Extended

    *I wonder if it's necessary to reactivate plugins each time? I guess I will do so unless I hear otherwise, and I'll keep checking this thread.

    Thanks very much from Catherine.

16. Catherine_B
    Member
    Posted 3 years ago #

    YAY -- DONE AND DONE. The four upgrades finished. Minor problems resolved by searching the error codes. I found that not copying all the files over caused little glitches, so on the last two I just copied the whole caboodle.

    What I learned from this was: Do copy the entire site first (like they say) - and don't skip over a bunch of upgrades, especially on 'automatic' like with godaddy, where there was no way to know what had gotten messed up. Of course, a total file copy (not just the database) would have saved all those hours.

    Many thanks to Whooami and Figaro!

    With best regards from Catherine.

Topic Closed

This topic has been closed to new replies.