Steps to reproduce:

1) Install a module or core and enable it (eg, drupal-7.0-beta1).
2) Update to a new version of module or core (eg, drupal-7.0-rc4).
3) Run update.php successfully.
4) Receive screenshot (before.jpeg).

With the attached patch, you aren't told that modules returned messages when they didn't. See after.jpeg. Any failed updates (or returned messages of any type) would still display properly, along with the module name.

The "Returned Messages" box still appears even if there were a no messages - but to fix that would require a bit of reorganization in the function as a whole. Thus, the one line patch - it's not perfect, but it removes a major UX wtf moment with very little possibility of breaking anything.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Tor Arne Thune’s picture

FileSize
34.41 KB

I can confirm that the patch works as described. Updated token 7.x-1.0-alpha2 to token 7.x-1.0-alpha3 and got the screen attached after running the database updates.

Bojhan’s picture

An empty box, lets just not display it then.

threewestwinds’s picture

FileSize
1.84 KB

Empty box hidden.

redndahead’s picture

Ok reviewed this and the latest patch seems like it would print like this

These modules have messages

Views
Query 7001
blah

Views
Query 7002
blah blah

Webform
Query 7001
blah

This patch changes it to.

These modules have messages

Views
Query 7001
blah

Query 7002
blah blah

Webform

Query 7001
blah

This does need a look over to make sure output is correct.

Status: Needs review » Needs work

The last submitted patch, 1013808-update_output-1.patch, failed testing.

threewestwinds’s picture

Status: Needs work » Reviewed & tested by the community
FileSize
17.74 KB
37.31 KB

EDIT: Correction: Those images are with #3 applied. Please read with this post with the fact in mind that I thought I was testing #4, but it was actually my own patch that I had applied (doh).

Here's a screenshot of a bunch of updates with #4 applied. There were many updates that returned nothing, and those modules (properly) did not display anything. Notice however that "taxonomy module" shows up twice.

The second screenshot again has a bunch of successful updates, this time without core hacked to return a bunch of junk. :) Notice the complete lack of misleading or empty text boxes.

So, it doesn't fix every bug in this screen - but it's still much better than what went before, and it does fix the opening issue that both @merlinofchaos, @webchick and I had noticed. Thus, RTBC, with the intention of a followup issue for 7.1 to address the (corner case) doubling of certain module names - it only comes up when a module has two updates run at once, and even then only id they both succeed and return messages.

threewestwinds’s picture

Cross posted with bot.

redndahead’s picture

Status: Reviewed & tested by the community » Needs review
FileSize
11.83 KB
8.34 KB
11.71 KB
9.74 KB
2.16 KB

This patch fixes a bad variable name and switching single quotes to double quotes for new line. Also here are some screenshots of it working. I'll be happy to post any additional screenshots you need.

redndahead’s picture

I tested locally and it passes the failing test.

threewestwinds’s picture

Status: Needs review » Reviewed & tested by the community
FileSize
18.07 KB

Code looks good, passed tests, screenshot when no modules return messages attached.

webchick’s picture

Status: Reviewed & tested by the community » Fixed

YAY! *So* glad to have this fixed. This has bugged me for months.

Committed to HEAD. :D

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.