mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #47518
[Bug 1758606] [NEW] User registration required fields missing "*"
Public bug reported:
Environment tested: Master
Browser tested: MS Edge (Virtualbox)
===================
Manual Test Script
===================
Test Steps:
1) User want to register
2) User does not do anything with 2 new Explicit consent switches
3) user fills in all other required fields correctly
Actual result: User gets an error message "Your account will not be
created when you do not consent to the privacy statement." and "Your
account will not be created when you do not consent to the terms and
conditions."
Expected result: these 2 new fields should have an "*" indicating it is
a required field or some other visual indication that the user has to
interact with the field
Recommend: marking 2 fields with "*" or making the "Please read the
privacy statement. If you do not consent to it, you cannot create an
account on the site." red o that users know action needs to be taken for
the 2 new Explicit consent switches.
Catalyst QA
** Affects: mahara
Importance: Undecided
Status: New
--
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/1758606
Title:
User registration required fields missing "*"
Status in Mahara:
New
Bug description:
Environment tested: Master
Browser tested: MS Edge (Virtualbox)
===================
Manual Test Script
===================
Test Steps:
1) User want to register
2) User does not do anything with 2 new Explicit consent switches
3) user fills in all other required fields correctly
Actual result: User gets an error message "Your account will not be
created when you do not consent to the privacy statement." and "Your
account will not be created when you do not consent to the terms and
conditions."
Expected result: these 2 new fields should have an "*" indicating it
is a required field or some other visual indication that the user has
to interact with the field
Recommend: marking 2 fields with "*" or making the "Please read the
privacy statement. If you do not consent to it, you cannot create an
account on the site." red o that users know action needs to be taken
for the 2 new Explicit consent switches.
Catalyst QA
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1758606/+subscriptions
Follow ups