-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EZP-30161 Update ezjscore token variable identifier #1420
Conversation
Care to explain why? And ideally also which issue this is possible regression from? |
@andrerom I have identified this issue when installing 2.4 with legacy bridge, check netgen/NetgenAdminUIBundle#27 (comment) "Alright, I will try to reproduce and record this sometime next week and I will post the video here. I have just installed eZP 2.4 yesterday and I am sure the form token extension is checking for "_token" instead of "ezxform_token" with legacy bridge." |
TODO: make the token identifier configurable. |
@thiagocamposviana I did a quick investigation and almost everything here is done already. So default form field name is Legacy Bridge already overloads that form field name based on the one used by Symfony: This PR only need small adjustment to get the form field name by calling Hence avoiding the hard coding of this here, and probably solve several token issues in the process (so 2017.12 branch here I guess) when running in symfony mode. Remaining question, @thiagocamposviana / @emodric is the name change of the |
Using a method to get the configured value could be the way, and we can introduce a second method to configure the Problem is however that these are not only hardcoded in PHP, but also in JS and templates, both here (in admin design) and in other extensions (ezmultiupload, ezie, ezflow):
|
Indeed, so what do you suggest? For token form field name we could have fallback logic to first looked for the default one then secondly for injected one. For |
Fallback logic where? I don't have any suggestions, especially for tpl and js parts :(
Probably we don't. I didn't go into details with it. |
In As in looking for default/old one first, then checking for additional "custom" field if set on |
That could work 👍 |
@thiagocamposviana Up for it, or you want one of us to take over on this? |
@andrerom I am good with you guys taking over this |
@thiagocamposviana When you have the time, please have a look and see if #1431 solves the issue for you, afaik you won't need any other changes. |
https://jira.ez.no/browse/EZP-30161
New versions should use _token and not ezxform_token_js