Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
Bartik theme
Priority:
Normal
Category:
Bug report
Assigned:
Issue tags:
Reporter:
Created:
7 Nov 2011 at 15:54 UTC
Updated:
12 Jul 2012 at 08:19 UTC
Jump to comment: Most recent file
Comments
Comment #1
webchickPosting on behalf of Jesse since she is behind some sort of evil anti-Drupal.org force-field atm:
The regression was introduced in http://drupalcode.org/project/drupal.git/commitdiff/ea1bd8becea0a4b214cb... (#790556: Make the Maintenance Page Kick Ass)
Comment #2
webchickAnd reviewing that issue, this was introduced at #790556-65: Make the Maintenance Page Kick Ass. Quoting:
So I think we need to set this to an empty string, rather than unsetting it, and a comment that explains why the heck we are doing that would be wonderful.
Comment #3
webchickThis should be pretty straight-forward.
Comment #4
jessebeach commentedSetting to 8.x dev. The patch will need to be ported to 7.x
Comment #5
jessebeach commentedchanged
to
$variables['site_name'] is still set, but it now empty, so the check for it in maintenance-page.tpl.php returns FALSE instead of failing and throwing an error.
Comment #6
jessebeach commentedmarking as need review
Comment #7
webchickYep, that looks right. can you toss a one-liner comment in there too above
if (!$variables['db_is_active']) {about why we're doing that?Comment #8
aspilicious commentedAdding tag, see #1334342: During update, Bartik throws an error that $site_name is not defined
Comment #9
jessebeach commentedComments added. I think this is why this code exists, but tim plunkett would be the person to ask for sure.
Comment #10
kisugiai commentedThanks Works for me
but i have a anothe question. i have two drupal installations the one use bartik as maintenece and the other uses seven as maintenance page where is this settet?
Comment #12
webchick#9: bartik_maintenance_page-1334344-9.patch queued for re-testing.
Comment #13
jessebeach commentedShould I just load the 7.x version of the patch here?
Comment #14
jessebeach commentedAlyx Vance, this patch only affects Bartik, not Seven.
Comment #15
kisugiai commentedthats i know its has not to do with seven.
my confusion is thats two Drupal7 installationen use two diffrent maintanance themes.
thats only an question why. i have found nothing to setup this.
eg. the xy.com use bartik and the yx.com use seven.
Comment #16
jessebeach commentedLet's make sure we don't hijack this issue with unrelated questions.
But just to answer this one, you can set your admin theme at the bottom of the Appearance tab form:
https://skitch.com/jesse.beach/gedhf/rockmelt-appearance-d8.drupal.dev
Comment #17
mstef commentedRerolled patch #9 to apply from a standard Drupal installation root - needed for drush make. (7.x)
Comment #19
aspilicious commented#9 still needs review for D8.
#17 is for D7
Comment #20
tim.plunkettHeh, I remember rerolling that original patch to unset it. Good catch.
Comment #21
jessebeach commentedRolled for D7. I just added '-d7.patch' to the patch in 17 to befuddle Testbot.
Comment #22
catchWorks for me and doesn't look testable. Committed/pushed to 8.x, moving back to 7.x
Comment #23
devin carlson commentedThe patch in #21 applied cleanly and made the same change as the original patch in #9.
I've uploaded the same patch as in #21 but with a different file name in order to trigger the test bot.
Comment #24
devin carlson commentedComment #25
webchickCommitted and pushed to 7.x. Thanks!
Comment #27
cweagansUpdating tags per http://drupal.org/node/1517250