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.
Currently the module tries to divine several things about the encryption used and sets those as the value to use or uses the value provided by the caller if the value is empty. In the case of the $options it doesn't do that. $options are a little different from the other values since they are an array so I think it makes sense to merge them if there are some in the original encryption serialized array. I set it so the calling code is overridden by the saved values which is consistent with the way other values behave.
Comment | File | Size | Author |
---|---|---|---|
#1 | 1834700_divine_options.patch | 740 bytes | greggles |
Comments
Comment #1
gregglesComment #2
gregglesI forgot to really lay out the benefits of this.
Currently you often have to do:
It would be nice if you could just do:
Comment #4
greggles#1: 1834700_divine_options.patch queued for re-testing.
Comment #5
gregglesNot sure why it failed at first. I filed #1834856: unexplained test failure on encrypt module (mcrypt extention issue?) about it.
I'll be trying this out more locally and will commit in ~2 weeks if there's no further advice.
Comment #6
gregglesNow fixed - http://drupalcode.org/project/encrypt.git/commit/34247cc