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.
After #932502: Changing allowed values in "List" fields was committed, sites using Entity module ended up with a WSOD.
While there was an actual mistake in Entity module, the site shouldn't have fatal'ed with a WSOD.
Attached patch fixes the problem.
Comment | File | Size | Author |
---|---|---|---|
drupal.user-field-info-alter.0.patch | 836 bytes | sun | |
Comments
Comment #1
pillarsdotnet CreditAttribution: pillarsdotnet commentedI was about to upload my own patch/fix, but i like yours better. (testing...) Works for me.
Comment #2
Damien Tournoud CreditAttribution: Damien Tournoud commentedAgreed that we should set good examples here.
Comment #3
alayham CreditAttribution: alayham commentedsub
Comment #4
alayham CreditAttribution: alayham commentedtested, problem solved.
Comment #5
sunNote that if you experienced this problem, then it's very likely that you also experienced or will also experience the other problem:
#996236: drupal_flush_all_caches() does not clear entity info cache
Comment #6
ryivhnn CreditAttribution: ryivhnn commentedPatch works :)
Comment #7
jpstrikesback CreditAttribution: jpstrikesback commentedSolves the Notice & the Fatal :) Marking this major - prior to applying the patch this issue killed fresh installs of install profiles like commerce-dev (Using Aegir)
Comment #8
webchickGenerally speaking, we want tests for this kind of bug fix, but since this is just robustifying an existing line I think this is fine.
Committed to HEAD. Thanks!
Comment #9
rszrama CreditAttribution: rszrama commentedThank goodness... I was freaking out over how I'd debug this just now. That's hit me in the past, so I'm glad core no longer assumes the key is there... the WSOD on install is rather disconcerting. : P