Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • CiviCRM Core CiviCRM Core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,444
    • Issues 1,444
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • CiviCRM CoreCiviCRM Core
  • Issues
  • #3471
Closed
Open
Created May 19, 2022 by eileen@eileen🎱Owner

Address parsing reporting on import - needed? reachable?

When importing contacts there is handling for USPS address parsing

My take on it is the USPS parsing has almost certainly stopped working and it is pretty hard to see how someone would implement their own (& why they wouldn't use a pre hook)

However, my proposal here is not to remove all USPS coding - just to remove REPORTING of rows that failed to usps code in the import. This involves a lot of code and slows down the import simply to put up a message that seems very marginally useful if it DOES work

image

image

Edited May 19, 2022 by eileen
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking