django-fields is not compatible with the django Sites framework (multiple settings.py files).

[erikcw]

I use the django sites framework to run several sites from the same application. Since each setting file has its own SECRET_KEY, the sites cannot share encrypted data. django-fields should accept a parameter or look for a var in settings.py to override this behavior with a custom key for the cipher. If it doesn't exist, then fall back on settings.SECRET_KEY.

I think this may be related to issue #1.

[svetlyak40wt]

Erik, feel free to implement this in your fork and send me a pull request.

[bltravis]

I would point out that the phrasing of this issue is, technically, incorrect. The incompatibility is not with the Sites framework, per se, but with your particular setup. That said, your suggestion of a dedicated setting with fallback is probably worth pursuing.

[bltravis]

I believe #40 might fix this issue, for the most part. You can now specify a secret key value as an argument in the field's constructor. If not specified, it will fall back to the value in settings.py.