upgrade problem from 6.1 to 6.2

dru-fan - April 11, 2008 - 07:57

After uploading new files, while trying to upgrade site went blank

Tried following:
a) $update_free_access = TRUE;
b) new installation
i) old db access changing db info from settings.php
ii) copied data from old db to new one

same result for all.

Thank you.

I did that last night without problem

aryanto - April 11, 2008 - 08:19

Here is what I have done last night:

1. Disable all caches
2. Put my site off line
3. Disable all non Drupal core modules
4. Switch the default theme to Garland
5. Backup the folder containing Drupal 6.1
6. Download and unpack Drupal 6.2
7. Replace all Drupal 6.1 files with Drupal 6.2 by copying them
8. Execute update.php via browser
9. Enable all non Drupal core modules
10. Switch the default theme to my own theme
11. Put my site on line
12. Enable all caches

So I didn't even touch MySQL database or settings.php. But maybe there is almost nothing useful yet in my site, a part from the layout containing Lorem ipsum, 6 nodes and 6 menu buttons. As I am still trying to figure out how Drupal actually works this last 2 weeks.

Hi

dru-fan - April 11, 2008 - 08:24

Thank you for quick response. If I have to do it again, I will surely follow your steps.
Now, I'm stuck in the middle. Do you have any other suggestions?

Restore everything

aryanto - April 11, 2008 - 08:40

Did you back up your MySQL database? If not then I think you are out of luck, as I beleive it is quite hard to revert the content in MySQL tables one by one.

If you did that, then just restore everything and re-do the upgrade again.

Update

Heine - April 11, 2008 - 08:21

You need to run update.php, and on the second page click the button 'Update'.

I don't know how to make this clearer in the update notes.
--
The Manual | Troubleshooting FAQ | Tips for posting | How to report a security issue.

Hi,

dru-fan - April 11, 2008 - 08:27

Yeah, I was trying to do that but suddenly page went blank.

Above mention steps are the ones I tried to retrieve my old installation.

Thank you.

Log

Heine - April 11, 2008 - 08:28

Same error...

hyrcan - April 21, 2008 - 03:17

This happened on a site to me just now as well. update.php comes up blank.

The reason for this is because I was lazy. In the past, even though the UPGRADE.TXT dutifully told me to disable all contributed modules (basically anything in your /sites/all/modules folder), the update.php script would kick of with no problems, happily changing what it needed to with out so much as a, hey btw... you want to disable this stuff.

So fiddling with a dev site I'm messing with I dropped 6.2 in place hit up update.php and got a blank white page. uh ho. My laziness will not be tolerated in time around it seems. :-/

Now. What do I do to get around it? Well, I had two options. I took the hard option (or easy if you're not scared of hitting the database).

First option, is if you have those old 6.1 files hanging out, drop them back into place, and cross your fingers and log in... then do what the UPRADE.TXT file tells you... the developers of Drupal didn't spend the time writing that file, including it in the distribution download taking up thousands of precious bytes (5002 it seems) for you to rush head long into Drupal upgrades not following those instructions. They give those instructions because they have to have a baseline to work with. The Core. They've tested upgrade.php with all the versions of the core of Drupal to make sure it works. It would be a nightmare to test that with every combination of random contributed modules.

*hangs head in shame*

Second option, which is what I did go into your system table and change `status` from 1 to 0 on any filenames that are `/sites/all/*`
Of course this assumes you've been using the /sites/all/modules for your contributed modules like a good little drupler... ;) Then run the update.php... then realize that you're no longer logged in and edit the settings.php to include $update_free_access = TRUE;

Then go to update.php and watch as the excellent ninja coding of the drupal teams hooks your site up with super ninja tools and sharks with lazer beams on their heads!

Hope this helps anyone stumbling in here trying to find out why update.php is blank.

Peace
Hyrcan

*sharks with lazer beams on their heads not actually included due to international lazer beam weilding shark treaties...or are just a delusion of the author's tired mind.

Thank you.

dru-fan - April 12, 2008 - 06:29

Thank you guys for help. I finally fixed it.

What was wrong and how did you fix it?

aryanto - April 12, 2008 - 09:30

I think it would be good for Drupal community if you explained what was wrong and how you fixed it. As you would definitely also want to know the solutions of any other the problems experienced by somebody elses, which are exactly the same as would you have.

So it is not for me I am writting this as I don't have any problems upgrading Drupal 6.1 to 6.2 :)

reinstall

dru-fan - April 12, 2008 - 15:52

I installed fresh drupal 6.2 and copied needed tables one by one from previous db backup.

Has anyone heard of Drupal

Ecrofirt - April 14, 2008 - 16:30

Has anyone heard of Drupal causing a HTTP 406 error when updating from one version to another?

I get said error when trying to go from 6.1 to 6.2, and I did exactly what aryanto suggested.

I made a thread about this last night, but this thread seems to cover things similar as well.

I got in touch with my host,

Ecrofirt - April 14, 2008 - 18:09

I got in touch with my host, and they confirmed that this seems to be the issue.

Thanks a lot for your help with that!

Might be a little late for

HotDrupal.com - April 16, 2008 - 02:57

Might be a little late for this, but ... your provider might have a database backup from before you tried to upgrade in case your db is hosed.

For instance, we do a mysqldump of all user databases once a night and compress the files. We keep these for maybe four days (regular backups much longer) for easy database restoration if something like this happens to a user.

Steve
HotDrupal

Upgrading 6.1 to 6.2

linuxpowers - April 16, 2008 - 08:27

I've been reading everything I can about this upgrade...I'm a newbie to ALL of this and I have a question before I start the upgrade process. Well, a couple if you don't mind!

First of all, you need to know that I have a test site (6.1) set up in a subdirectory I created and it's working great. I'm in the process of figuring it all out, since I just had it installed about two weeks ago.

BTW, it was originally installed through cPanel by fantasico, so I'm not sure if doing a manual upgrade will be effected by that original installation.

But, since I've had this site up and running, I've made some CSS changes to all the default themes and I was thinking I should pull out those CSS files and replace them after the upgrade...assuming all goes well. Am I approaching that issue correctly?

Also, I went to cPanel and downloaded a backup of my DB and a backup of my subdirectory (alias & filters) to my desktop. I'm assuming this is in case things go wrong and I need to put things back...am I right about that as well?

And just one more thing about my backups, in cPanel, they downloaded in a zip form ".gz"! If I need to restore these files, cPanel allows for this but I only get three choices to upload files to restore, "Home Directory", "MySQL DB" and "Email Domain Forwarder/Filter". Which one of these would I use to restore my subdirectory and do I need to unzip it before uploading?

I forgot to mention, I also added some directories under /site/all for organizational reasons and I am thinking I need to pull them aside until after the upgrade as well, is that also correct?

Thanks in advance!

Is this the correct update procedure?

Dick Underwood - April 19, 2008 - 16:14

During the last month I set up my first Drupal site using Drupal 6.1, and I was so impressed with how easy it was I then converted another couple of my sites to Drupal. I used Fantastico (yes. I know) but everything was fine.

Blow me. I'd just finished when along came Drupal 6.2!

I've read all the stuff I can find about upgrading, including upgrade.txt, drupal.org/upgrade, and various forum posts. I'm worried about security issues, but I'm also worried about losing my sites!

I've put together notes of what I think I need to do, but before I actually do this, is there someone who can provide some feed-back as to whether it's correct or not? Preferably someone who has used Fantastico in the past and then done a manual upgrade.

I want to do this for my site at www.poems-verses.com I’m starting with this site because it’s the smallest, and because, whilst it has several books and pages, it has no files uploaded to it. I’m also only using standard modules and theme. Doing this site first should provide the confidence and experience to do my larger sites.

1. Set my site to offline mode.

2. Backup my MySQL Database to my desktop (using cPanel, by clicking on ‘phpMyAdmin’, then ‘export’)

3. Backup my whole website to my desktop (using cPanel,by clicking on ‘Backup Wizard’, then ‘Home Directory’)

4. Using Fantastico, delete Drupal.

5. From the Drupal site (not via Fantastico) download Drupal 6.2 to my desktop, then ftp it all to my site, except for the ‘sites’ folder. (I don’t have a ‘files’ folder on this site)

6. Find the ‘sites’ folder on my desktop that had previously been saved from Drupal 6.1, and ftp it to my site.

7. Check and change, if necessary the .htaccess and robots.txt files

8. Run update.php

9. Log in to website. Re-enable modules and theme.

10. Return the site to online mode.

That’s it (I think) but is the above correct. Does anyone know?

Upgrading 6.1 to 6.2 if you've used Fantastico

Dick Underwood - April 20, 2008 - 18:21

I'd used Fantastico to add 6.1 (just before the 6.2 update)

I've just updated my site from 6.1 to 6.2 and I've put full details at http://drupal.org/node/248998 for anyone who needs the details.

mod/thm addons

solaureum - April 21, 2008 - 16:55

Thanks for the rundown, but you're a little vague about the add-on modules/themes...did you/must we disable and re-enable all of these manually on either side of update?

when using MySQL 4.1.22-standard

AndriaD - April 22, 2008 - 13:40

I'm wondering if the version of MySQL makes any difference in this process.

I was on a host that ran MySQL 5; had no problems whatever updating from Drupal 6.1 to 6.2.

I am now on a host that's running MySQL 4.1.22-standard, and although the Fantastico-installed 6.1 runs just fine, it DOESN'T advise me about the 6.2 security update (as I was advised when I was running 6.1 on the other host). I tried to run this update last night on a fresh install of 6.1, and the update process simply "hung" while it was on that animated bar; when I tried to load Drupal after that, it gave me a fatal error, so, since it was a fresh install, I removed it and started over this morning with a new install of 6.1 -- but I'd really rather not have to go thru all this again, so I thought I would inquire RE: the version of MySQL.

Thx,
Andria

ok no problems

AndriaD - April 22, 2008 - 14:36

It appears that my worries about the MySQL version were groundless; the update went smoothly. I suspect my issues were due to incomplete propagation of my domain name, from the old nameservers to the new, and/or issues related to caching because of the nameserver update. *WHEW*

Andria

upgrade with drupal-6.2.tar

newuserKN - May 15, 2008 - 16:58

Following the update instructions...please help me:
#4. switch to a core theme. Does this mean make a core them default? I'm using Cameleon do I have to switch (make default) to Garland?
#5 Disable all custom and contributed modules.
I have only core optional ones checked. Do I have to uncHeck those? Are they considered custom?
#6 Remove all old files and directories from the Drupal installation directory.
Delete all my files? The .tar file doesn't seem to replace any files that I have. do I really need to delete everything in the root?
#7 Unpack the new files and directories into the Drupal installation directory.
drupal-6.2.tar.gz seems to be just one file. I opened it with jedit. What is there to unpack?
#8 Copy your backed up "files" and "sites" directories to the Drupal
installation directory. If other system files such as .htaccess or
robots.txt were customized, re-create the modifications in the new
versions of the files using the backups taken in step #1.
Is this necessry if I don't delete the original files?

9. Verify the new configuration file to make sure it has correct information.
What configuration file? What am I looking for to see if it is correct?

I downloaded drupal-6.2.tar but i don't know where to upload it to. And there's nothing to extract or unpack. It seems to be one file. Do I upload it to the root? Is there anything to get rid of first? I only have core optional mudles checked should I uncheck them?

.tar files are archives

Ecrofirt - May 18, 2008 - 00:45

.tar files are archives (like .zip files). You need to get a program that can open them up.

I suggest 7zip or WinRAR.

 
 

Drupal is a registered trademark of Dries Buytaert.