When we are in ANY maintenance mode, we do not want to allow aggregation.

When the database is down and the site is in error maintenance mode, the error pages would be attempting to do aggregation without having any way to update the state, causing additional load. The fallback maintenance page does not have any business attempting to aggregate anyway.

This check for != update mode had originally been intended in #199946: Stale css+js files on upgrade to prevent both miscaching and exposing the drupal version, but it should have been taken out when the logic was changed to use an incrementing number.

You can see the original code that led to this in #199946-22: Stale css+js files on upgrade.

Comments

bdragon created an issue. See original summary.

bdragon’s picture

bdragon’s picture

Status: Active » Needs review
fabianx’s picture

Status: Needs review » Reviewed & tested by the community
Issue tags: +Drupal 7.70 target

RTBC - Looks great to me!

fabianx’s picture

Issue tags: +Needs change record
bdragon’s picture

change record drafted @ https://www.drupal.org/node/3018664

heddn’s picture

Reviewed the CR. It looks good.

joseph.olstad’s picture

This is a smart change, thanks.

izmeez’s picture

Status: Reviewed & tested by the community » Needs review
StatusFileSize
new1.13 KB

Patch in #2 no longer applies. Attached is a quick re-roll.

mcdruid’s picture

Status: Needs review » Reviewed & tested by the community
Issue tags: -Drupal 7.74 target, -Needs change record +Pending Drupal 7 commit

LGTM

fabianx’s picture

RTBC + 1 again :) - this happened on a real site :)

  • mcdruid committed 021554e on 7.x
    Issue #3015223 by bdragon, izmeez, heddn: Never use aggregation in...
mcdruid’s picture

Status: Reviewed & tested by the community » Fixed
Issue tags: -Pending Drupal 7 commit

Thanks everybody!

Status: Fixed » Closed (fixed)

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

quietone’s picture

Published change record