I have had the first dev version for awhile now.
When i tried to upgrade to the latest normal version, i got a fatel error, i upgraded the same way i have done everything else, upload new version, it over writes the old version and run update.php (i know update.php isnt always needed but its habit i guess)
I had to search thru the past releases to get my site back for now, but i would like to upgrade asap.

error : it was saying an error about file field handler, sorry i couldnt give more info but i cant have my site down for too long, its my wifes outlet :)

Any help would be apprecated

Comments

yched’s picture

yched commented
Status: Active » Closed (duplicate)

http://drupal.org/node/277968

Draven_Caine’s picture

Draven_Caine commented
Status: Closed (duplicate) » Active

i didnt see it as a duplicate since my error was on a diffrent line, but when a fix lands for the other thread i'll gladly try it.

yched’s picture

yched commented
Status: Active » Postponed (maintainer needs more info)

Please make sure you're using the latest RC release : http://ftp.drupal.org/files/projects/cck-6.x-2.0-rc2.tar.gz, after *deleting* (not overwriting) the cck folder that currently lives on your server.

Please also make sure that you're using the latest Drupal core dev code (http://ftp.drupal.org/files/projects/drupal-6.x-dev.tar.gz, or latest CVS DRUPAL-6 branch), not the 6.2 release.

If this doesn't fix it, we'll need more specific information about the exact behavior and error message you're seeing.

kbell’s picture

kbell commented
Version: 6.x-2.0-beta » 6.x-2.0-rc2

I had the same problem. I upgraded from rc1 to rc2 and it brought the entire site down with a fatal error on line 255 of content.views.inc (the only thing that changes in the rc2 release, judging from the release notes).

I performed the same kind of upgrade the previous user did, i.e. replacing changed files rather than deleting the folder and starting over. After reading this thread I deleted the folder and started over, but still got a fatal error. I ran update.php then and everything seemed to stabilize. So, frustrating and scary, but at least it worked. I always run update.php after any module change or upgrade, but it was disturbing to have ths site go down completely as soon as the module was copied over.

Thanks,
Kelly

yched’s picture

yched commented
Status: Postponed (maintainer needs more info) » Fixed

Yes, rc1 was unfortunate [edit : but only lived a couple of minutes], rc2 was ok except for people that put their contrib modules in the main /modules folder instead of /sites/xxx/modules (which is *highly* recommended, but not enforced)
So we now have rc3...

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.