I've been working on a Drupal v7 project for some 6 months it was based on Drupal v7.0 and a few of the modules were playing up so I decided to attempt an upgrade via Drush 4.x. After a few hours today with Drush,
Drush upgraded to Drupal 7.14 by merely downloading the upgrade to a new DIR and removing all the previous D7.0 core etc. I've mySQL backups (using phpmyadmin 3.3.10deb1) which I can import to recover all the input work done over the past months. I'm not bothered about the current D7 versions, I just want to recover all my setup such as Roles, Ubercart permissions, Panels, Views and basic nodes such pages, content.
Ideally, I'd like to go to Drupal v7.14, but if I need to go back to Drupal v7.0 then fine. I REALLY DON'T want to back track over what I have already done.
I'm trying at this moment numerous 'hacks' to get the site back to how it was on my localhost (Ubuntu LAMP).

I'm working localhost on an Ubuntu 11.04 LAMP (No Wamp/xxamp) so remote upgrading is not an issue.

Can anybody advise (other than jumping off a bridge! LOL) on how to get the project back on track.
Cheers,

Paul B

Comments

john.oltman’s picture

There's no way to know what state your system is in so really hard to tell you what to do. What I would recommend is you restore back to the starting point, make sure the site works the way it used to before you messed with it, and then do the following steps:

Backup database, then

1. Download a fresh copy of D7.0 to a temporary location
2. diff -rw drupal-7.0-temporary-location path-to-my-current-d7.0-installation > diff.txt (this tells you how your localhost system differs from a fresh D7.0 download)
3. Download D7.14
4. Examine diff.txt and apply the differences to D7.14 (at a minimum this will involve replacement of the "sites" folder in the D7.14 folder)
5. Move your current d7.0 installation to a backup location (this is a single command)
6. Move the new D7.14 folder to where the previous d7.0 installation was (using previous folder name)
7. Load the upgraded site in your web browser
8. Run update.php

At this point you have a working D7.14 site. You then can selectively upgrade modules that have new versions. This isn't necessary though and is really a separate issue.

If things go badly you restore the previous folder and database and hire someone else to do it.

paulbuk’s picture

Thank you John for taking the time to reply. The site is only be devleoped on a localhost (Ubuntu 11.04 using LAMP via root/usr/www
I've now spend the best part of a whole day. The frustrating thing is not being able to simply get going again. Part of the process of learning is for me to get back into work myself having left FE lecturing I suppose (-:
It's true, Drupal does have a large learning curve LOL.

I've done a fresh install and am trying now to manually import and salvage all the data entries such as Nodes, Field setup, Panels/Views, Ubercart etc. 6 months effort in 2 days.
Paul B

end user’s picture

I know it doesn't help now but years ago I eventuality learned that when working with upgrading sites that I've worked on for a long time I'd backup the DB and the whole public html folder. If I ever couldn't get the site backup after an upgrade glitch I'd just remove the upgraded site and unzip the old one to the public html directory and restore the db.

paulbuk’s picture

Thanks. I really should have know better! Having been in IT for 25 years (mainly then on M$win), it was just one of those 'dumb' moments. I, for some reason hadn't install the Migrate module, a silly oversight. I'm one of those guys who builds his own pcs etc, etc and likes to learn, I've certainly 'learned' a new lession today LOL, still more Drupal experience.
Today, (the day after) I've decided to go for a fresh clean install (with Migrate installed!), it wasn't the content but the hours lost (probably 60 hours, maybe more over a 6 month period). Most of it was learning content, but still one doesn't like to lose that time.

Maybe I'm getting old. {';'}