mahara-contributors team mailing list archive

[Mahara Bot <1853387@xxxxxxxxxxxxxxxxxx>]

Patch for "19.10_STABLE" branch: https://reviews.mahara.org/10696

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1853387

Title:
  jsform field defaults to no when field is disabled

Status in Mahara:
  Fix Committed
Status in Mahara 19.10 series:
  Fix Committed
Status in Mahara 20.04 series:
  Fix Committed

Bug description:
  An issue was picked up on Administration Menu->Configure site->Site
  options->Security Settings which could be a bigger issue with the way
  JSForms processes.

  Preconditions:
  In the config.php file have "recaptchaonregisterform" set to true, i.e $cfg->recaptchaonregisterform = true;
  Test:
  1. Log in as site admin and go to Administration Menu->Configure site->Site options->Security Settings.
  2. Scroll to "reCAPTCHA on user registration / contact us forms" and it should be set to "yes" as it reads from the config.php file. It should also be disabled.
  3. Submit the page then view the Security Settings again.
  Expected result:
  The disabled "reCAPTCHA on user registration / contact us forms" button still shows "yes".
  Actual result:
  The disabled ""reCAPTCHA on user registration / contact us forms" button now shows "no"

  This issue was also seen in admin/site/networking.php during work on
  https://reviews.mahara.org/#/c/10616/2.  Removing the jsform => true
  in the pieform stopped the disabled form fields defaulting to their
  'false' values, i.e when the page is submitted.

  Mahara: 19.10_STABLE
  Browsers: Firefox and Chrome
  DB: Postgres

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1853387/+subscriptions