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.

CommentFileSizeAuthor
drupal.user-field-info-alter.0.patch836 bytessun

Comments

pillarsdotnet’s picture

pillarsdotnet commented
Status: Needs review » Reviewed & tested by the community

I was about to upload my own patch/fix, but i like yours better. (testing...) Works for me.

damien tournoud’s picture

damien tournoud commented

Agreed that we should set good examples here.

alayham’s picture

alayham commented

sub

alayham’s picture

alayham commented

tested, problem solved.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

Note 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

ryivhnn’s picture

ryivhnn commented

Patch works :)

jpstrikesback’s picture

jpstrikesback commented
Priority: Normal » Major

Solves 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)

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Status: Reviewed & tested by the community » Fixed

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

rszrama’s picture

rszrama commented

Thank 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

Status: Fixed » Closed (fixed)

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