The picture pretty much says it all... When a module has dependencies on other updates that haven't run... or are incapable of running, then this is how they are shown. THey are unreadable.
screenshot

Comments

benbon’s picture

Thanks for this info

Stevel’s picture

Issue summary: View changes
Status: Active » Needs review
StatusFileSize
new1011 bytes

This patch should fix that behavior by adding the 'messages' class to the div.

poker10’s picture

Status: Needs review » Reviewed & tested by the community

Tested this manually and it works great, thanks! Moving to RTBC.

If someone else want to test this manually, the fastest way is to define an empty hook_update_N() in one module .install file, then add a hook_update_dependencies() to the same .install file and require a non-existing update from other module. Like this:

function comment_update_dependencies() {
  $dependencies['comment'][7010] = array(
    'block' => 7010,
  );
  return $dependencies;
}

Then the update.php will display the dependency warning like the one in the IS. After applying the patch the warning is readable again.

  • mcdruid committed d7b56576 on 7.x
    Issue #2090185 by Stevel, generalredneck, poker10: Warning span...
mcdruid’s picture

Status: Reviewed & tested by the community » Fixed

Thanks everyone!

Status: Fixed » Closed (fixed)

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