When adding a new Encryption Profile at admin/config/system/encryption/profiles/add without any encryption method modules installed, submitting the form correctly shows the error message:
No encryption method selected.
However, the red validation-error highlight is applied to the Encryption Key field, not the Encryption Method field — even though Encryption Method is the empty/invalid field and Encryption Key is correctly filled in. This is misleading and makes it look like the Key field is the problem, when it isn't.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | image (11).png | 52.57 KB | gurkawal |
| #2 | 3623929-validation-error-field-highlight.patch | 993 bytes | gurkawal |
| encryption_issue.png | 55.35 KB | dkmishra |
Comments
Comment #2
gurkawal commentedHi @dkmishra,
I reproduced the issue on Drupal 11.
When saving an encryption profile without selecting an encryption method, the form correctly displays:
No encryption method selected.
However, the validation error highlight was incorrectly applied to the Encryption Key field instead of the Encryption Method field. This was misleading because the key could be valid while only the encryption method was missing.
Cause:
In EncryptionProfileForm::validateForm(), all entity validation errors were being attached to encryption_key:
$form_state->setErrorByName('encryption_key', implode(';', $errors));
Fix:
The patch maps each validation error to the correct form field, such as encryption_method or encryption_key, before calling setErrorByName().
Verified after applying the patch:
Error message: No encryption method selected.
Red validation highlight appears on Encryption Method, not Encryption Key.
Tested on Drupal 11.4 with Encrypt 8.x-3.3.
Comment #3
gurkawal commented