You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Theoretically, the only way this form can have errors is if the CSRF token is invalid/expired, so it's not a major issue, but when it happens, instead of having the form rendered with an error message, we have an exception:
Since modules can add new elements/input filters to this form, this can happen in other scenarios as well.
The easiest way to trigger the bug is to decrease the CSRF timeout in application/src/Form/Initializer/Csrf.php to 1 second and to start a batch edit, select either "Public" or "Not public" in "Set value visibility", then submit the form.
This is due to the fact that it tries to render 'value' and 'set_value_visibility' as hidden inputs whereas the values we just submitted for these elements are arrays
The text was updated successfully, but these errors were encountered:
These two elements are custom built in common/property-form-batch-edit.phtml
and will POST arrays. The form knows about the elements via hidden inputs,
which expect strings. If the form has an error, we must set the input values
to empty strings or there will be errors.
Theoretically, the only way this form can have errors is if the CSRF token is invalid/expired, so it's not a major issue, but when it happens, instead of having the form rendered with an error message, we have an exception:
Since modules can add new elements/input filters to this form, this can happen in other scenarios as well.
The easiest way to trigger the bug is to decrease the CSRF timeout in
application/src/Form/Initializer/Csrf.php
to 1 second and to start a batch edit, select either "Public" or "Not public" in "Set value visibility", then submit the form.This is due to the fact that it tries to render 'value' and 'set_value_visibility' as hidden inputs whereas the values we just submitted for these elements are arrays
The text was updated successfully, but these errors were encountered: