Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I created a content type that utilized a number of field types that required additional modules to be installed. The modules for
these field types were disabled unbeknownst to me, and I attempted to add one of these content types and came up with the
error listed in the subject line. The error is coming from the content_set_empty() function in content.module.
Could someone please add some checking to confirm that the required module is available and throw a nicer error if it isn't ?
Comments
Comment #1
yched commentedNope, a field type where we cannot find hook_content_is_empty() should rightfully break.
The real question is : how did you manage to create a field whose field type was not available. That shouldn't be possible, so it would be interesting to know how you did it.
Comment #2
darrellduane commentedI disabled the module that supports the field type after I created it.
I've changed this to a feature request.
Could someone please add some checking to confirm that the required module is available and throw a nicer error explaining the need for the module to be installed and enabled if it isn't ?