Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-8282

address parsing should handle digit-dash-digit (421-16) in street_number + street_number_suffix

    Details

    • Type: Bug
    • Status: Done/Fixed
    • Priority: Minor
    • Resolution: Fixed/Completed
    • Affects Version/s: 3.4.0, 3.4.1, 3.4.2, 4.0.0, 4.0.1, 4.0.2
    • Fix Version/s: 3.3.7
    • Component/s: Core CiviCRM
    • Labels:
      None

      Description

      street address parsing for street_number + _suffix does not handle values where there is a number-dash-number
      attached patch corrects it. there's a second piece to the patch where we run all values through stripSpaces (we had found double spaces and leading/trailing spaces sometimes retained in the data.

      the regex change is as follows -
      we were defining the streetNumAndSuffix as alphanumeric through and including the first non-word character. that mean the value ended at spaces (which is largely what we wanted) – OR at punctuation (dashes).
      this change breaks only at spaces, thus allowing dashes to be part of the parsing process thereafter. a few additional adjustments to then support this change.

        Attachments

          Activity

            People

            • Assignee:
              lcdweb Brian Shaughnessy
              Reporter:
              lcdweb Brian Shaughnessy
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: