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.
Screen shot of black background Configure screen

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...

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jhodgdon’s picture

I really felt like the "Congratulations" message was appropriate after I managed to fill in the fields on that screen and continue. ;)

dawehner’s picture

Lovely! I like how Drupal tries to be environmental friendly these days.e

njbarrett’s picture

Hmm, 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.

njbarrett’s picture

Seeing 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).

nod_’s picture

Confirmed. A refresh of the page makes the style appear. Cache issue somewhere?

jhodgdon’s picture

njbarret: #3 and #4 are separate issues. Please search the issue queue and if they are not already filed, file new issues. Thanks!

njbarrett’s picture

Title: Screen is black and completely unreadable in Configure page after install » Screen is black and completely unreadable in Configure page after install on standard profile

@jhodgdon my bad, will do

Aki Tendo’s picture

This 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.

jhodgdon’s picture

@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.

Dom.’s picture

Also 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.

alexpott’s picture

@Dom.

Also because on that issue given on #9, you cannot install a module with default configurations for optional modules which could be nice.

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 not config/install. That's the whole point of that change.

Dom.’s picture

Oups!

alexpott’s picture

Status: Active » Needs review
FileSize
1.33 KB
4.41 KB

The 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.

dawehner’s picture

Ah, now this is looking much better!

+++ b/core/includes/install.core.inc
@@ -1611,21 +1611,13 @@ function install_profile_modules(&$install_state) {
-  $theme_handler = \Drupal::service('theme_handler');
-
-  // ThemeHandler::install() resets the current list of themes. The theme used
-  // in the installer is not necessarily in the list of themes to install, so
-  // retain the current list.
-  // @see _drupal_maintenance_theme()
-  $current_themes = $theme_handler->listInfo();
-
   // Install the themes specified by the installation profile.
   $themes = $install_state['profile_info']['themes'];
-  $theme_handler->install($themes);
+  \Drupal::service('theme_handler')->install($themes);
 
-  foreach ($current_themes as $theme) {
-    $theme_handler->addTheme($theme);
-  }
+  // Ensure that the install profile's theme is used.
+  // @see _drupal_maintenance_theme()
+  \Drupal::service('theme.manager')->resetActiveTheme();

Its really good to know that the theme manager is working properly in the early stages here.

The last submitted patch, 13: 2458925.12-test-only.patch, failed testing.

Dom.’s picture

Hi,

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 !

jhodgdon’s picture

Thanks very much for testing, Dom! I was just about to try it but you saved me the trouble. Much appreciated!

alexpott’s picture

So who is going to take the next step with this issue then?

alexpott’s picture

Btw 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 :)

jhodgdon’s picture

Status: Needs review » Reviewed & tested by the community

This 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!

  • catch committed 92ee8c5 on 8.0.x
    Issue #2458925 by alexpott: Screen is black and completely unreadable in...
catch’s picture

Status: Reviewed & tested by the community » Fixed

Committed/pushed to 8.0.x, thanks!

alexpott’s picture

Status: Fixed » Closed (fixed)

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