Wrong behaviour: When a content type is being exported (by the means of the features.module) with a maxlength-enabled field, maxlength.module is not added to the list of dependencies, though the exported field definition does have the maxlength-enabled cruft. If one enables this exported feature without explicitly enabling maxlength.module, the maxlength functionality will be lost.

Expected behaviour: The maxlength.module should be automatically added to the dependencies of the exported feature in such a case, thus avoiding the need to manually enable the maxlength.module.

@see #982736: Insert does not get autodetected by Features for this kind of issue in insert.module's queue (there's even a patch there).

Comments

cedewey’s picture

cedewey
he/him
Primary language English
Location Denver, CO
CreditAttribution: cedewey at DevCollaborative, LLC commented
Issue summary: View changes
Status: Active » Closed (works as designed)

We are putting a feature freeze on the Drupal 7 version of the module, so I'm marking this Closed (works as designed). Thank you reporting this issue.

Drupal 8/9 has a new configuration management system which does away with the need for Features in many circumstances. If you haven't already, I encourage you to update your website to the latest version of Drupal.