Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
To reproduce: Install with Standard profile.
When you get to the step where you are supposed to configure your site, you cannot read the screen. Screen shot attached. It's got a nearly-black background with nearly black labels. All you can really see is the text fields.
Um. Something got broken... I saw this earlier today on simplytest.me, and thought maybe it was a fluke of that site. But I just did a git pull, cleared out my database, and reinstalled, and had the same problem on my local site.
Sorry if this is a duplicate. I searched for "black" and didn't find anything...
Comment | File | Size | Author |
---|---|---|---|
#13 | 2458925.12.patch | 4.41 KB | alexpott |
#13 | 2458925.12-test-only.patch | 1.33 KB | alexpott |
blackscreen.png | 31.42 KB | jhodgdon |
Comments
Comment #1
jhodgdonI really felt like the "Congratulations" message was appropriate after I managed to fill in the fields on that screen and continue. ;)
Comment #2
dawehnerLovely! I like how Drupal tries to be environmental friendly these days.e
Comment #3
njbarrett CreditAttribution: njbarrett commentedHmm, using Minimal profile I got to the configure page OK, but when clicking the submit at the end of the configure form I just get taken to a server 500 error page.
Comment #4
njbarrett CreditAttribution: njbarrett commentedSeeing this error:
Warning: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in Symfony\Component\Yaml\Inline::evaluateScalar() (line 503 of core/vendor/symfony/yaml/Symfony/Component/Yaml/Inline.php).
Comment #5
nod_Confirmed. A refresh of the page makes the style appear. Cache issue somewhere?
Comment #6
jhodgdonnjbarret: #3 and #4 are separate issues. Please search the issue queue and if they are not already filed, file new issues. Thanks!
Comment #7
njbarrett CreditAttribution: njbarrett commented@jhodgdon my bad, will do
Comment #8
Aki Tendo CreditAttribution: Aki Tendo commentedThis has only occurred in the last week or so - I first noticed it Monday. I'm going to try to find last known good this morning and figure out what happened.
Comment #9
jhodgdon@Aki - alexpott just bisected and announced in IRC that the cause was #2090115: Don't install a module when its default configuration has unmet dependencies apparently.
Comment #10
Dom. CreditAttribution: Dom. commentedAlso because on that issue given on #9, you cannot install a module with default configurations for optional modules which could be nice.
Note that if you refresh the "configuration page" which is black during the install process, it get's fine as usual and thus usable. This leverages the issue I guess.
Comment #11
alexpott@Dom.
Can you post on #2090115: Don't install a module when its default configuration has unmet dependencies as to want you mean. I think this is probably just because the configuration being provided by the module has not been moved to the correct location. Optional config needs to go in
config/optional
notconfig/install
. That's the whole point of that change.Comment #12
Dom. CreditAttribution: Dom. commentedOups!
Comment #13
alexpottThe problem is to do with how the active theme is set in the installer - the code in
_drupal_maintenance_theme
is a bit skewiff. This patch fixes the bug and adds a test. In a followup I will combine StandardInstallerTest and StandardTest but changing StandardTest to use InstallerTestBase instead of WebTestBase is a bit tricky and lots of out-of-context changes would be needed.Comment #14
dawehnerAh, now this is looking much better!
Its really good to know that the theme manager is working properly in the early stages here.
Comment #16
Dom. CreditAttribution: Dom. commentedHi,
Patch applied from fresh Drupal and tested manually: install went well, no black screen.
Also had a look at the code : Drupal code convention followed (check with PHP CodeSniffer).
However, I'm not able to judge code solution itself, axelpott #13 defines code as "skewiff" and induce some further work to remain on test conversion. For this reason I'm not taking responsability for flaging status to reviewed and tested just adding this : RTBC+1 for me !
Comment #17
jhodgdonThanks very much for testing, Dom! I was just about to try it but you saved me the trouble. Much appreciated!
Comment #18
alexpottSo who is going to take the next step with this issue then?
Comment #19
alexpottBtw the screenshot in the issue summary is the what bartik looks like when used as the installation theme :) - I think we can safely say that Bartik is not meant for that :)
Comment #20
jhodgdonThis looks good. Code is clear. Has been tested manually. Has test that fails without patch and passes with patch. Critical and we need to not have a beta with a Black Screen of Unreadability. Let's do it!
Comment #22
catchCommitted/pushed to 8.0.x, thanks!
Comment #23
alexpottCreated followup #2459699: Merge StandardInstallerTest and StandardTest