Jump to:
| Project: | Drupal core |
| Version: | 7.x-dev |
| Component: | update.module |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (cannot reproduce) |
Issue Summary
I just updated my site from 7.x-beta1 to 7.x-beta2, and afterwards used the Modules > Upgrade feature to update my installed modules. The upgrade manager found updates for 4 modules (Backup & Migrate, Google Analytics, Views, WYSIWYG), and one theme (Zen). I chose to update all 5 and then got the attached feedback, stating
Update failed! See the log below for more information
, but the "log below" showed only successes, and Recent Log Messages has nothing to report. (See D7-upgrade-failure-UI attachment.)
Note: all upgrades were from the dev or recommended versions of the modules as of Oct. 8, to the latest dev versions as of 10/23. The site is local on WAMP running PHP 5.2.11.
At first I thought that the error had been with the Backup & Migrate module, since it wasn't represented in the list, but when I checked the Status Report, it indicated that I needed to run update.php, and it turned out to be Views that required the db upgrade.
So from a user perspective there are several problems here:
- An upgrade error was reported but not specified (on that page or anywhere else I can find)
- Not all upgraded modules were listed in the report
- Running update.php was needed, but there was no message indicating that.
- There was a link to run update.php, but it's buried in such a way that it appears to be a subset of the Zen information, so I didn't even notice it until I started to say in the issue that there wasn't a link at all.
- links at bottom don't distinguish between important and optional tasks
I know that people have been working on D7 for a long time so there are undoubtedly many complexities around different possible outcomes on this page that I don't understand. But with that caveat, I'd like to offer a possible direction for improving points 3-5 (above) from a user perspective (See D7-module-upgrade-feedback-revised, attached).
Let me know if points 1-2 are distinct enough (being code issues rather than UI issues?) that I should file a separate issue for those.
| Attachment | Size | Status | Test result | Operations |
|---|---|---|---|---|
| D7-upgrade-failure-UI.png | 87.15 KB | Ignored: Check issue status. | None | None |
| D7-module-upgrade-feedback-revised.png | 49.04 KB | Ignored: Check issue status. | None | None |
Comments
#1
Designating this as the issue to fix #2 above.
Of the 5 issues listed above:
#1 is a duplicate of #605292: propagate failure during batches in update manager
#3 and #4 are duplicates of #606190: Fix handling of database schema updates in update manager workflow
#5 is a duplicate of the general "fix this up" issue at #602484: Fix the report page when authorize.php completes an update manager operation
#2
Can anyone reproduce this? It hasn't appeared on my own install and so I'm not sure where to begin hunting this down.
#3
I suspect this issue will be shaked out when the bugs that comment 1 listed are resolved. But just in case you're keeping score:
(2.) is the only issue that isn't similar to issues reported in other bug reports.
#4
Repeat: Can anyone reproduce this? I've never seen it, either. Without reliable steps to reproduce, I think we'll have to close this as "cannot reproduce"...
#5
I couldn't find any other issues in the queue describing a similar problem, so closing for now.