Problem/Motivation
I cannot find the field encryption setting in the field UI. I suspect that the changes in the field forms are responsible for this:
In Drupal 10.2 there is no storage tab, when editing fields. Since Field Storage Configuration Form is now a subform within Field Configuration Edit Form, the checkbox for encrypting fields is missing/never shown in Drupal 10.2.
See: https://www.drupal.org/node/3386675
I am not experienced enough with Drupal modules to customize the module myself.
It would be great if someone could look into this and provide a patch.
| Comment | File | Size | Author |
|---|---|---|---|
| #31 | сompatibility-with-drupal-10.2-3421958-31.patch | 18.84 KB | rznasa |
Issue fork field_encrypt-3421958
Show commands
Start 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:
Comments
Comment #2
efes commentedI'm experiencing the same issue.
Field Encrypt was almost the first module, which was installed on a brand new Drupal 10.2.3 site. Tried with Real AES and Sodium too, but the checkbox never shown in the editing form of the entity.
Comment #7
hmdnawaz commentedPlease use the MR 41 for Drupal 10.2
Comment #8
hmdnawaz commentedAll the tests are passed for Drupal 10.2 now.
Comment #9
pozzo-balbi commentedLast Development version: 3.1.x-dev is from 9 Feb 2023 at 15:50 UTC. Is it possible to release an updated version that works with Drupal 10.2? Thanks
Comment #10
ptmkenny commentedComment #11
ptmkenny commented@pozzo-balbi Have you tested this MR and checked if it works? It would help if people tested this before it is committed.
Comment #12
pozzo-balbi commentedI'm still very new. I manually used the code to update the file "field_encrypt.module" and I could use field encrypt with new Drupal 10 release of pubkey_encrypt module. So it appears to do what it is supposed to do. Creating a dev version, would make it easier for all to install and test. If people don't complain for 2 weeks, update the release version.
Comment #13
ptmkenny commentedWelcome to Drupal. If you downloaded the patch, applied it, and it works for you, please state that in your post. If, after your testing and reviewing the code, you feel confident that the fix is the right one, you can also change the issue status from "Needs review" to "Reviewed and tested by the community." This can help the patch get committed faster, as it shows the module maintainer that at least one person has successfully applied the fix and it worked for them.
In the case of this module, it does not seem to be actively maintained at the moment; the last commit to the dev branch, which you can see on the project page, was over a year ago. However, it's quite likely that the module will be updated for Drupal 11, and other issues that have been marked RTBC ("Reviewed and tested by the community") will hopefully be evaluated for inclusion at that time.
Comment #14
iaacristobalI just tested the latest field_encrypt-3421958 branch and the Encryption checkboxes still do not display on my end. I am using the latest Drupal version to date (10.2.5)My mistake, i downloaded the default branch. That's why it isn't working yet.
I just cloned the field_encrypt-D10.2-compatability branch and found that the Encrypt fields are working, and the data is encrypted as well in the database.
I'm not 100% Confident with this yet as this is my first time reviewing a module. But for anyone interested in testing, this tutorial is how I did it.
Comment #15
iaacristobalComment #16
efes commentedYes, the field_encrypt-D10.2-compatability branch is really working under Drupal 10.2.5.
It would be good, if this could be merged, at least to the dev version of the module.
Thanks for your work!
Comment #17
ptmkenny commentedBumping this to critical because the module cannot be configured on the current version of Drupal.
Comment #18
dmiric commentedIs this merged? I can't see any field options on D 10.3
Comment #19
ptmkenny commentedNo, it isn't merged. At present, you need to apply a patch from the MR to use the module.
Comment #20
jerrac commentedMerge !41 worked for me just now on a dev site. Drupal 10.2.7.
Comment #21
pozzo-balbi commentedTested with 10.3 and it is working.
Comment #24
ptmkenny commented@ranjith-mahendran Please don't change the visibility of the branch without a comment stating why. The
field_encrypt-D10.2-compatabilityis the current leading solution to this issue.Comment #25
ranjith-mahendran commented@ptmkenny Apologies, It won't happen again in future.
Comment #26
carolpettirossi commentedI was facing this issue with Drupal 10.3.1. The MR solved the problem. Thanks a lot!
Comment #27
romainj commentedPatch working for me too.
Comment #28
alexpottWe'll need to change the minimum version the module supports which is a great idea.
Comment #29
alexpottGoing to get this released in 3.2.0
Comment #31
rznasa commentedAdded as patch from MR.