I have just started working with Features, so I am not sure if this is intended or just not an issue. Basically during the course of attempting to 'feature-ize' my site I have created and re-created feature modules many times. I have split parts out of features and added new parts in. In the course of this dependencies have changed from one version of the feature to the next.

Now, what I have noticed is that in the system table the data stored in the 'info' column (the serialized text from .info) for one of my features has never updated; even though I have enabled, disabled, over-written, and reverted the feature many times. This particular feature is also a dependency for several other features and although the Features management screen shows the feature is enabled the entry in the system table has status '0'.

So far everything is still working fine, I just discovered this troubleshooting another issue and thought I would post it in case there is an explanation or it is something I should be concerned about.

Comments

hefox’s picture

Features could force a module rebuild, like system did for modules page (not sure if does it anymore), which course made that page slow to load.

Runnign drush updb -y; or update.php will refresh it.

hefox’s picture

Issue summary: View changes
Status: Active » Fixed

Status: Fixed » Closed (fixed)

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