Tighten up input validation on payments form zip/postal code field
Closed, DuplicatePublic
Actions

Assigned To

None

Authored By

	jgleeson
	Sep 10 2020, 6:42 PM

Description

It looks some characters that aren't part of a valid zip/postal code are making it through current input validation. Let's tighten this up to only allow characters that we expect would make up a zip/postal code.

See T262232 for context and examples of the issue.

Related Objects

Mentioned Here: T262232: Donations queue consumer failed - Invalid character input in postal code

Event Timeline

jgleeson created this task.Sep 10 2020, 6:42 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 10 2020, 6:42 PM

jgleeson updated the task description. (Show Details)Sep 10 2020, 6:44 PM

• DStrine moved this task from Triage to Sprint +1 on the Fundraising-Backlog board.Sep 14 2020, 2:46 PM

• DStrine moved this task from Sprint +1 to Sprint +2 on the Fundraising-Backlog board.Sep 15 2020, 5:40 PM

• DStrine closed this task as a duplicate of T262232: Donations queue consumer failed - Invalid character input in postal code.Oct 1 2020, 5:01 PM

Tighten up input validation on payments form zip/postal code field Closed, DuplicatePublicActions

Description

Related Objects

Event Timeline

Tighten up input validation on payments form zip/postal code field
Closed, DuplicatePublic
Actions