Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Here are the steps that I think need to be taken to prepare the Encrypt module for a 2.1 release. Once that release is done, I'd like to focus development on a Drupal 8 version.
- #2281341: Integration with Features to allow for settings export
- #2401681: Pass configuration to encryption method callback as argument
- #2386819: Encrypt/Decrypt and cache clear issue with CTools plugin system
#2418753: Provide a generic mcrypt pluginDeprecate the basic (no library) encryption methodChange the default encryption method to McryptAllow mode to be selected in Mcrypt settings- #2486217: Make configuration available in the key callback function
Comments
Comment #1
gregglesUpdating link styles.
Looks like a great list to me.
Comment #2
gregglesComment #3
rlhawkI've altered the list of items for 2.1. Once #2486217: Make configuration available in the key callback function is committed, we should be ready for a 2.1 release candidate.
With the Drupal 8 version of Encrypt underway, I'm eager to get started on the next full version (3.x), which will not be backward compatible with 2.x.
Comment #4
rlhawkThe last item was committed, so I've created a 2.1-rc1 release. The changes in this version are not related to Encrypt's core functionality, so there should be no compatibility issues with prior versions.
Comment #5
rlhawk