...as per title. I just noticed this now. I see that the table is rendered differently in 7.x and that there is now a "dedicated" <td> with a status-icon class, but that is only populated with icons for the parent <tr>s with classes warning or error, not the ones with ok class.

CommentFileSizeAuthor
#3 drupal_1086818_3.patch162 bytesJosh The Geek
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

aspilicious’s picture

aspilicious CreditAttribution: aspilicious commented
Version: 7.x-dev » 8.x-dev

Moving to 8.x, bugs get first fixed in there.

Josh The Geek’s picture

Josh The Geek CreditAttribution: Josh The Geek commented
Assigned: Unassigned » Josh The Geek
FileSize
drupal_1086818_3.patch162 bytes

So the image just needs to be removed? If so, patch.

Josh The Geek’s picture

Josh The Geek CreditAttribution: Josh The Geek commented
Status: Active » Needs review

The same patch should work for 7.x, too, if needed.

Status: Needs review » Needs work

The last submitted patch, drupal_1086818_3.patch, failed testing.

Josh The Geek’s picture

Josh The Geek CreditAttribution: Josh The Geek commented
Status: Needs work » Needs review

Just ignore testbot, I think it's complaining the patch is weird because I just deleted a file.

cweagans’s picture

cweagans
He/Him
Primary language English
Location Boise, ID, USA
CreditAttribution: cweagans commented
Status: Needs review » Needs work

Uhh, no. Do not delete that file. That's used in the dblog listings.

Josh The Geek’s picture

Josh The Geek CreditAttribution: Josh The Geek commented

Oh, I'm stupid. It needs to go back. Duh. On it.

Josh The Geek’s picture

Josh The Geek CreditAttribution: Josh The Geek commented
Assigned: Josh The Geek » Unassigned

Okay, apparently I am no good at css. Sorry for the mistake. Relinquishing this issue.

amateescu’s picture

amateescu CreditAttribution: amateescu commented
Version: 8.x-dev » 7.x-dev

The Garland theme has been removed from D8: #911054: Remove Garland from Core

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
CreditAttribution: klonos commented

Yep, it now has a new home in contrib: http://drupal.org/project/garland

joachim’s picture

joachim CreditAttribution: joachim commented
Version: 7.x-dev » 8.0.x-dev
Component: Garland theme » system.module
Issue summary: View changes

This is nothing to do with Garland, or indeed any theme -- it's system module's output.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

quietone’s picture

quietone CreditAttribution: quietone as a volunteer commented
Version: 8.9.x-dev » 7.x-dev

This isn't relevant to the redesigned status page in Drupal 8/9. It was redesigned in #665790: Redesign the status report page and committed in Feb 2018.

If this is a desired change it would be for Drupal 7.