Compatibility with Drupal 10.2: Encrypting fields not possible in the UI

I'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.

hmdnawaz → changed the visibility of the branch field_encrypt-3421958 to hidden.

Please use the MR 41 for Drupal 10.2

All the tests are passed for Drupal 10.2 now.

Last 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

@pozzo-balbi Have you tested this MR and checked if it works? It would help if people tested this before it is committed.

I'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.

Welcome 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.

I 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)

Yes, 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!

Bumping this to critical because the module cannot be configured on the current version of Drupal.

Is this merged? I can't see any field options on D 10.3

No, it isn't merged. At present, you need to apply a patch from the MR to use the module.

Merge !41 worked for me just now on a dev site. Drupal 10.2.7.

Tested with 10.3 and it is working.

ranjith-mahendran → changed the visibility of the branch field_encrypt-D10.2-compatability to hidden.

ptmkenny → changed the visibility of the branch field_encrypt-D10.2-compatability to active.

@ranjith-mahendran Please don't change the visibility of the branch without a comment stating why. The field_encrypt-D10.2-compatability is the current leading solution to this issue.

@ptmkenny Apologies, It won't happen again in future. I'm having latest version of 'Field Encrypt' module in my existing Drupal 10 website. I did module upgrade methods like decrypt all the fields and uninstall the module again install the module but now 'Fields Encryption' option not showing to fields. I get the clone from 'field_encrypt-D10.2-compatability' replaced it and now 'Fields Encryption' option showing to fields so this is the fine way to fix this issue in existing Drupal 10 website? Because I was compared both code 'field_encrypt-D10.2-compatability' and 'Field Encrypt' latest version looks different. If I used 'field_encrypt-D10.2-compatability' to fix this issue later upgrade the 'Field Encrypt' module fixed codes will be gone or not?
Thanks in advance.

I was facing this issue with Drupal 10.3.1. The MR solved the problem. Thanks a lot!

Patch working for me too.

We'll need to change the minimum version the module supports which is a great idea.

Going to get this released in 3.2.0

Automatically closed - issue fixed for 2 weeks with no activity.