Upgrading from Views 6.12 to 6.14 fails with the error:

An HTTP error 0 occurred. http://icteach.org/update.php?id=65&op=do

v6.12 is known to require a security update, so this means Drupal websites continue to be susceptible to an attack.

This needs to be fixed.

Comments

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Postponed (maintainer needs more info)

Why do you not update to views 2.13?

In general without giving information on an issue it simply can't be fixed.

mkmk’s picture

mkmk commented

Upgrading to 6.13 also fails, with the same error:

An HTTP error 0 occurred. http:///update.php?id=66&op=do

Here is the error message recorded in admin/reports/dblog:

warning: array_pop() [function.array-pop]: The argument should be an array in /var/www/drupal/update.php on line 313.

mkmk’s picture

mkmk commented
Priority: Normal » Critical

This is still not fixed, and all Drupal websites using views still vulnerable.

mkmk’s picture

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

The maintainer has info.

dawehner’s picture

dawehner
Primary language German
commented

Please read http://drupal.org/node/1336126#comment-5221378 again
It's hard to fix an error which you can't tell us more then a non-saying error message.

You know views 2.13 simply can't cause the problem because it's just a really small change compared to 2.12, which simply can't break update.php
Maybe you update views wrong, but that's hard to guess.

dawehner’s picture

dawehner
Primary language German
commented

Maybe it helps you to enable displaying of php error messages. A simple "HTTP error 0" isn't that helpful, but if you have full php error's added there might be the important parts shown.

The error you showed is actually a warning not an error, but seems to be some kind of problem of update.php or your way of updating.

mkmk’s picture

mkmk commented

How can I enable full php errors? There is nothing in Apache's error.log
The errors I reported are the errors Drupal reported.

Visiting update.php shows that views module is at version 6010 and needs to be upgraded. The upgrade fails.

"Updating

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 0 occurred. http:///update.php?id=67&op=do"

"The update process was aborted prematurely while running update #6010 in views.module. All errors have been logged. You may need to check the watchdog database table manually."

I checked the watchbdog table and there's nothing related to the update ther.

mkmk’s picture

mkmk commented

Clearly the error is due to the views module.

It is the upgrade from 6010 to the current that breaks. Minor change from 6.12 to 6.13 or not, the required upgrade breaks.

Views breaks.

merlinofchaos’s picture

merlinofchaos commented

Unfortunately, that error message isn't helpful.

We haven't seen this error in local testing.

Without having some idea what's breaking, we can't fix the error.

Clearly the error is due to the views module.

Incorrect. Clearly the error happened during update 6010. That does not mean it was due to the Views module. While one might surmise that it is likely, saying that "Clearly this is so" is a logical leap.

Also, since 2.13 does not have actually include views update 6010 that actually adds even *more* trouble to your theory that clearly Views is responsible. In fact, Views has *no* database updates between 2.12 and 2.13, so this cannot possibly be preventing you from using the security update.

merlinofchaos’s picture

merlinofchaos commented

I recommend you try this.

On your database where you're running Views 2.12 perform an update.php -- make sure all other modules are up to date.

Then update Views and only Views. (Do not disable the module).

Then run update.php again.

Does this still happen?

mkmk’s picture

mkmk commented

You are correct, it was a logical leap.

Running update.php while views 2.12 is still the version running leads to this error message too. This suggests some other piece of code is causing this.

mkmk’s picture

mkmk commented

I wish upgrading web-apps were easier and more reliable.

If anyone has thoughts on how to best accomplish this, I'd love to hear them.

mustanggb’s picture

mustanggb commented
Issue summary: View changes
Status: Active » Closed (won't fix)