I've been experiencing several different failures when trying to update Views using the core Update Manager. The Update Manager has worked fine for some other modules, but is failing with both Views and at least one other module I'm using, Colorbox. In trying to sort out the problems, I've taken to just attempting one module at a time, when there are multiples with updates available.
Sometimes not all the files have gotten installed, in some instances resulting in Fatal Error bricking of the site. I've fixed this by updating the via the old FTP method I use for D6. But what's the most vexing is when there's apparent success using the Update manager and the module reports that it still needs to be updated. I'm experiencing the same issues with Colorbox, fwiw.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | colorobx-update-manager-error-screenshot.png | 112.53 KB | Anonymous (not verified) |
Comments
Comment #1
esmerel commentedI'm not sure how this is a views problem rather than an update manager problem, since update manager is failing in two places.
I'm going to guess this is a duplicate of #976912: MD5 hashes do not match on releases
Comment #2
j. ayen green commentedI am having the same issue. It had been working for me. Now, it shows CCK, Ctools, Views and XML Sitemap needing updating. When I launch it, whether for all the above or just one (any), the first module in the list (or the only, if only one is selected) appears in /tmp/update-cache but the process stops there, the page shows Preparing to update, with no change in the progress meter, and stays that way.
Comment #3
j. ayen green commentedComment #4
rfayComment #5
Anonymous (not verified) commentedWhen I try to update any module with colorbox 1.0-beta1 enabled I receive the following javascript error
$("a, area, input", context).filter(".colorbox").once("init-colorbox-processed").colorbox is not a functionand the update fails.
Comment #6
frjo commented