Feature deployed fields not triggering encryption.

From 💬 Existing data not encrypted when field is selected for encryption Closed: outdated .

So I've run into a similar issue to this, but not via the same path this user took.

Using this module in a standard fashion where you enable it on a field either earl in the process, or at a distinct point on a specific site works without issue. However, sites are more dynamic than this. What if you have a live site collecting unencrypted data and you're working towards deploying encryption.

Features is a standard method for deployment, and when I tested deployment with features, features updated the field in a fashion that never actually triggered field_encrypt_do_encrypt().

Our workaround for this is that I've written a custom batch enable module that batch enables encryption on the modules instead of relying on features to deploy. This in turn triggers field_encrypt_do_encrypt() properly and all fields wind up encrypted.

This doesn't really help define the solution much, but may shed light on some of the problem occurring for some users?