field_encrypt 4.1.0-beta1

Bug fixes

First release with support for Drupal 11.3

Contributors (2)

alexpott, ptmkenny

Changelog

Issues: 1 issues resolved.

Changes since 4.0.0 (compare):

field_encrypt 4.0.0

Bug fixes
New features

Official release with security coverage

Contributors (1)

ptmkenny

Changelog

Issues: 1 issues resolved.

Changes since 4.0.0-beta2 (compare):

field_encrypt 4.0.x-dev

Bug fixes

This branch is only for Drupal 11.1 and 11.2. From Drupal 11.3, please use the 4.x branch and Field Encrypt 4.1+.

field_encrypt 4.0.0-beta2

Bug fixes
New features

Computed Field compatibility

Contributors (4)

joachim, megakeegman, mlncn, ptmkenny

Changelog

Issues: 1 issues resolved.

field_encrypt 4.0.0-beta1

Bug fixes

No major issues reported during alpha, so moving to beta

Need someone using computed field to test #3517810: Error when computed_field module fields are present

Contributors (1)

ptmkenny

Changelog

Issues: 3 issues resolved.

field_encrypt 4.0.0-alpha2

Bug fixes

Should now work on Drupal 11.2

Contributors (5)

alexpott, ptmkenny, swirt, swirtMiles, tame4tex

Changelog

Issues: 6 issues resolved.

field_encrypt 4.0.0-alpha1

Bug fixes
New features

Adds compatibility with Drupal 11.1 and greater.

If you added hook implementations field_encrypt_ENTITY_TYPE_ID_insert() and field_encrypt_ENTITY_TYPE_ID_update() these can now be removed as the module adds the hooks for you with using eval().

If updating the 3.2.x then you must run updatedb as part of the update.

field_encrypt 3.2.0

Drupal 11 compatibility and drops Drupal 9 compatibility as it is not supported.

Note that this is not compatible with Drupal 11.1.x yet.

field_encrypt 3.1.0

New features
Unsupported

Drupal 10 compatibility
Minimum version 9.4

field_encrypt 3.0.0

New features
Unsupported

A stable 3.0.0 release of Field Encrypt. For the first time this module is opting into Drupal's security coverage and having a stable release.

This release is a complete re-architecture from 8.x-2.x and represents a massive performance increase. Another highlight is that it supports encrypting entity base fields. However this means that there is no upgrade path from 8.x-2.x. In order to upgrade you have to:

field_encrypt 3.0.0-alpha2

Bug fixes
Unsupported

This release is a massive refactoring of the Field Encrypt module. It is not compatible with 8.x-2.x and there is no straight forward upgrade path

The highlights of this release are:

field_encrypt 3.0.0-alpha1

Bug fixes
New features
Unsupported

This release is a massive refactoring of the Field Encrypt module. It is not compatible with 8.x-2.x and there is no straight forward upgrade path

The highlights of this release are:

field_encrypt 3.0.x-dev

New features

Changes how the module works to significantly improve performance. See #3162309: Save encrypted data as part of the entity and not as a separate entity.

Note that in order to upgrade from 8.x-2.x you need to decrypt all existing entities and completely uninstall the module.

field_encrypt 8.x-2.0-alpha2

Bug fixes
New features
Unsupported
  • Drupal 9 support
  • Drupal ^8.7 support for uncacheable fields
  • Fixed bug with Drupal commerce and the settings page.

field_encrypt 7.x-1.0-beta2

Bug fixes
Unsupported

#2028081 by caiovlp: Adding revision support.
#1949320 by caiovlp: Now deleting entries from the encrypt table whenever an entity or revision is deleted..

field_encrypt 7.x-1.x-dev

Initial DEV release.

Remember don't rely on this module to encode sensitive data.

This is only a DEV snapshot.

DO NOT USE IN A PRODUCITON SITE

Subscribe with RSS Subscribe to Releases for Field Encryption