Closed (fixed)
Project:
Views (for Drupal 7)
Version:
6.x-2.0-alpha3
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
17 Mar 2008 at 18:45 UTC
Updated:
2 Apr 2008 at 10:22 UTC
An unrecoverable error has occurred. You can find the error message below. It is advised to copy it to the clipboard for reference.
Please continue to the error page
An HTTP error 406 occurred. http://soldierx.com/sxdev2/update.php?id=6&op=do
Ran update script as usual.
Comments
Comment #1
merlinofchaos commentedPrrrrobably this isn't a big deal. I'm not sure how you could even have gotten a 406 error, tho. I'm not even sure what a 406 error is, I'd have to go look it up. But the update.php doesn't do much if you upgraded from alpha2; mostly it's meant to facilitiate upgrading from Views 1.
Comment #2
merlinofchaos commentedI believe a recent submitted patch fixed this error, so this should be fixed in cvs now.
Comment #3
jamm commentedI realize this issue is closed and there may well be a fix in cvs. The errors I received are real php errors, not http. I just want to put this info out there in case it makes sense at another point in time.
I received 2 errors when running update.php after upgrading only views. My setup is as follows:
Drupal 6.1 (Clean Install)
-> Devel 6.x-1.6
-> CCK 6.x-1.x-dev (Mar-15-08)
-> Contemplate 6.x-0.4-2
-> Views 6.x-2.0-alpha2 --> now alpha3 after upgrade
MAMP -> {Apache 2.0.59, MySQL 5.0.41, PHP 5.2.3}
Like I said fresh install of Drupal. Fresh install of Views alpha 2. I created 3 custom content types w/ CCK and 1 view {page}. I saw the new alpha3 release and decided to upgrade to get more features.
I after unpacking alpha3 source I ran update.php.
Error 1:
Error 2:
If this is a Drupal Core problem I will post there just let me know.
Based on this I take it I can just ignore the errors:
Comment #4
karens commentedProblem #3 is fixed in the dev release but the fix didn't make it into alpha 3. And it won't cause you any problems with your setup. It was just because there should have been an empty array returned to the upgrade code.
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.