Checkbox and OptionSet fields attempt to place validation errors in
.middleColumn to align them with the label, but in some custom themes
this is not available, so the error is swallowed instead. Instead, we
should place it in the main wrapping .field element as a fallback.
"Uncaught TypeError: Cannot read property 'data' of undefined
Was being reported when attempting to submit a form, which would
then trigger the "are you sure" functionality which should only
show when attempting to browse away from a page when changes to the
form have been made.
After testing it seems that having multiple user defined forms on a page
has already been added as a feature. However various load time dynamically
generated javascript segments had not been adapted to suit. Now they
have.
Also fixed a variable that no longer exists in the external requirements
from preventing a webpack build.
Mostly to do with translations, however the errors meant the front end
forms largely didn't work at all. Some of this was to do with the scoping
of `this` in es6 arrow functions, compared to the legacy code with entwine
that uses the fuller `function` definition. Reinstate missing dependency
for translations to function too.