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
Current use of print_small_button() generates a complex GET URL showing the form security token. It would be better to use print_form_button() so the token is handled as hidden form parameter.
Moreover multiple tokens are generated (one per issue), which is not efficient,
The text was updated successfully, but these errors were encountered:
Initial attempt to fix this (see 787eaa8) actually does not work - the Detach button always throws APPLICATION ERROR 2800 - Invalid form security token.
The problem persists even after fixing the problem with the invalid token (see 634277d).
This is because print_form_button() currently does not work with action URLs generated by plugin_page(), see MantisBT issue #28533.
This change has to be reverted for now and put on hold until the upstream problem has been fixed, probably in MantisBT 2.26.0 (PR mantisbt/mantisbt#1753).
Trying to detach an Issue from a Changeset always results in
APPLICATION ERROR 2800 - Invalid form security token, even when using
a valid token.
This is because print_form_button() currently does not work with action
URLs generated by plugin_page(), see [1].
So we revert to original behavior of using print_small_button() (as it
was before commit 787eaa8), but keeping
the single form security token implemented in commit
634277d.
This change can be reverted again, once the upstream issue has been
fixed.
Issue #372
[1]: https://mantisbt.org/bugs/view.php?id=28533
Current use of print_small_button() generates a complex GET URL showing the form security token. It would be better to use print_form_button() so the token is handled as hidden form parameter.
Moreover multiple tokens are generated (one per issue), which is not efficient,
The text was updated successfully, but these errors were encountered: