Stop displaying an email profile field as one of the normal fields
Bug #1858512 reported by
Robert Lyon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
High
|
Unassigned | ||
18.10 |
Fix Released
|
High
|
Unassigned | ||
19.04 |
Fix Released
|
High
|
Unassigned | ||
19.10 |
Fix Released
|
High
|
Unassigned |
Bug Description
The profile block treats the email field as special and only allows one email to be displayed.
However if the artefactids for the normal fields (eg firstname) ends up containing an id for an email field it causes problems as you cannot unset it from displaying.
I'm yet to work out how the array can end up with an email id but I have seen client sites where this has happened.
To avoid displaying the extra email artefacts I've created the following patch
https:/
Changed in mahara: | |
importance: | Undecided → High |
status: | New → In Progress |
milestone: | none → 20.04.0 |
Changed in mahara: | |
status: | Fix Committed → Fix Released |
no longer affects: | mahara/20.04 |
To post a comment you must log in.
copied from a comment in the patch:
I've found a way to replicate:
have a user with it's email
login as this user
create a view with a 'Profile information', select the email and save
add a new email address through Profile -> contact information and save
validate the new email address and select it to be the primary email address for the account
remove the old email address
go back to the view with the Profile information block
result:
Debug message "Artefact with id X not found"