Better handling of Pieforms validation failure in block modal
Bug 1560329: We were neglecting to rewire the "cancel/remove"
button on a block config after a Pieforms validation failure.
A pieforms validation failure (when you're using Pieforms'
jsforms feature) actually replaces the current form with a
new one, rather than just inserting error messages into the
existing form.
Change-Id: Ie3fa440595b08cc5a49cb89cb7ca95bcfa02c2db
behatnotneeded: Not easy to test with Behat
(cherry picked from commit ac21cd81495d12f277a55d97245ed2dc0bc414fd)
Reviewed: https:/ /reviews. mahara. org/7076 /git.mahara. org/mahara/ mahara/ commit/ ce695f4b453fa85 51cbff532cf578e 550e42f4f0
Committed: https:/
Submitter: Robert Lyon (<email address hidden>)
Branch: 16.10_STABLE
commit ce695f4b453fa85 51cbff532cf578e 550e42f4f0
Author: Aaron Wells <email address hidden>
Date: Tue Mar 22 18:56:14 2016 +1300
Better handling of Pieforms validation failure in block modal
Bug 1560329: We were neglecting to rewire the "cancel/remove"
button on a block config after a Pieforms validation failure.
A pieforms validation failure (when you're using Pieforms'
jsforms feature) actually replaces the current form with a
new one, rather than just inserting error messages into the
existing form.
Change-Id: Ie3fa440595b08c c5a49cb89cb7ca9 5bcfa02c2db 277a55d97245ed2 dc0bc414fd)
behatnotneeded: Not easy to test with Behat
(cherry picked from commit ac21cd81495d12f