How to continue with this one?

I would set validation = TRUE by default and review the places where encryptsave is used to review if validation should be turned off.
Also, validation, at least for encryptsave, should maybe not be applied to encripted fields?

I didn't see it was reported : https://github.com/LimeSurvey/LimeSurvey/pull/2149

new function : public function encryptSave($runValidation = true, $attributes = null)

Else : i give my opinion previously. In my opinion : all model->attribute must be decrypted transparently (and save as crypted transparently too).

It need a lot more developement here, and surely broke some plugin :)

@DenisChenu PR looks good to me, could you merge the target branch in to check if theres any issues.

3 years after ....

https://github.com/LimeSurvey/LimeSurvey/pull/3596#issuecomment-4170053358

There are still issues where validations are not used.
It's done, and not used

When a mandatory question is left unanswered and user clicks next, I see answers in responses view encrypted.

I can't reproduce

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=40568

Fixed in Release 7.4.0+260928