Details
-
Bug
-
Resolution: Fixed
-
Critical
-
5.1.0rc1
-
None
Description
In legacy mode, we use the symfony csrf protection field name to configure ezxformtoken. The issue is that as documented in ezformtoken/README.rst, we recommend this sort of code:
var _token = '', _tokenNode = document.getElementById('ezxform_token_js');
Since we were using the default configuration, the field name was _token, with ezxform, and extensions using the hardcoded name couldn't find the token and add it to their requests.
Attachments
Issue Links
- discovered while testing
-
EZP-20659 [Image Editor] Server error when applying watermark
- Closed