I know it is not really a bug. But we use webform_encrypt, and the patch to encrypt all webform fields. We work for government, and webform data should be encrypted allways. But then webform_options_limit does not work because it uses a raw query at the form results, and then they won't be decrypted and the element keys will be returned encrypted. So every entry is unique.
* install and setup webform_encrypt
* create a form with radio options, make sure it is encrypted
* add the webform_options_limit handler
* test with some submissions
Create an option to choose if the form is encrypted.
If it is not encrypted, just use the raw sql-queries. If the form is encrypted, use the entity queries.
| Comment | File | Size | Author |
|---|
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #3
liam morlandWebform 6.2.x in nearing EOL and receives only critical bug and security fixes.
Comment #4
joshahubbers commented@liam morland: I understand, but we are currently on 6.2. I will port this to 6.3 when it is finished and we start upgrading to Drupal 11.
Comment #5
joshahubbers commentedAfter review we decided it would be better to add the option to use the entity query so the module can use the more efficient raw sql query when a form is not encrypted.
Comment #7
joshahubbers commented@liam morland: I added a mr to the 6.3.x branch which is exactly the same as the 6.2.x mr. Is that ok?
Comment #8
joshahubbers commentedComment #10
liam morlandThat is fine. You could also just change which branch is targeted by the MR.