Problem:
Imagine the following case:
1. On your local installation - create a CT add serial field to it, export everything to features. Commit to GIT.
2. Go to a new installation / environment of you site, pull the code and enable the feature.

Due to correct dependencies, the feature will enable the module.
The problem is that after the enable process, when Drupal starts to create the CT, it seems that it does not know for the new field type. At this moment it triggers an exception...

This is due to the field info cache that is holding stale static data.

Solution:
Clear the static cache on hook_install.

Patch is coming...

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ndobromirov created an issue. See original summary.

ndobromirov’s picture

Status: Active » Needs review
FileSize
663 bytes

Here is the patch. It implements the proposed solution in the description.
It also solved the described problem.

BR, Nick.