Tried following your steps in UPGRADE.txt today to upgrade from 4.6 to 4.7-BETA and got a 411 Error when I went to actually execute the update.
I had to resort turning the access check off since I didn't have a session in IE and then using IE (didn't test with an older version of Firefox, not sure if that would have worked of not) and it worked fine. Using IE is not good for us running LINUX.
Thanks!

Comments

Amazon’s picture

Amazon CreditAttribution: Amazon commented

http://cvs.drupal.org/viewcvs/drupal/drupal/UPGRADE.txt?view=markup

You could also try the instructions at http://drupal.org/upgrade/tutorial-introduction

Thanks for posting this issue. You needed to be logged on as Admin 1 when backing up your database.

Cheers,
Kieran

Zen’s picture

Zen CreditAttribution: Zen commented
Project: » Drupal core
Version: » 4.7.0-beta1
Component: usability » update system
Priority: Critical » Normal

"411 : Length Required : The "Content-Length" is not defined. The server will not accept the request without it."

@rimshot: can you please test this again with the current update script? The update system has had something of an overhaul in the interim.. And please also provide your server details..

Thanks
-K

rimshot’s picture

rimshot CreditAttribution: rimshot commented

Sorry it took me a while to respond to your last posting. I was able to complete the upgrade it was just too bad that I had to use a second browser to complete it. Without taking my system and rolling back to 4.6 and then trying it again I won't be able to retest this. I just downloaded 4.6 and tried the upgrade to 4.7 beta3 and had no problems upgrading (as I'm sure you have tested this hundreds of times). Server details... Are you talking about OS? I am running Linux Fedora Core 3.
Thank you for taking the time to look into this issue and respond. I really appreciate it. I guess for now I would suggest we chalk this bug up as "not able to reproduce".

Jaza’s picture

Jaza CreditAttribution: Jaza commented
Version: 4.7.0-beta1 » 4.7.0
Status: Active » Closed (fixed)

Closing as it looks like it was only an issue with 4.7-beta-1, and was fixed as the new update system matured.