#3493710: Installing with Safari 18.2 causes a WSOD started the cleaned but the night is dark and full of terrors and we have found more issues around the same kind of problem: a parallel request might cause ExtensionList to cache and store in the state the profile being installed and then things go seriously pear shaped.
Erm, no.
Just drupal_flush_all_caches.
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #3
phenaproximaDiscussed in Slack and I am convinced that, although the more aggressive cache flush is a ding for performance, that concern is outweighed by the utterly baffling shittiness of a cache that has been accidentally primed with garbage during the install process, rendering Drupal non-functional unless you are able to
drush cr.Comment #5
phenaproximaComment #7
phenaproximaMaddeningly, I had to revert this because it turns out that flushing all caches wipes the session, forcing you to log in after the installation is complete. It's not clear why this happens, and it also seems to be semi-random (affecting 11.1.x but...not 11.2.x? maybe? it's not clear).
drupal_flush_all_caches()is a very aggressive cache wipe so this probably makes sense to revert for now and postpone until there is a CI pipeline with test coverage.