CRM-7741 selecting primary phone fields via profiles are misleadingly named and configurable

    Details

    • Type: Bug
    • Status: Done/Fixed
    • Priority: Trivial
    • Resolution: Won't Fix
    • Affects Version/s: 3.3.0, 3.3.1, 3.3.2, 3.3.3, 3.3.5
    • Fix Version/s: Unscheduled
    • Labels:
      None

      Description

      We've first discovered this at a 2.0.6 install, but managed to reproduce it on http://drupal.demo.civicrm.org/ too.

      Steps to reproduce:

      Result:
      Only one of the phone numbers is displayed (selected from the db)
      http://drupal.demo.civicrm.org/civicrm/profile/view?reset=1&id=104&gid=12

      We'd expect that this selects the appropriate type of phone number belonging to the primary location (like other location fields) but instead it selects the phone marked as primary, which is technically correct but doesn't seem to work the way other stuff does.

      Suggested solution is to rename civicrm_phone.is_primary to civicrm_phone.is_prefered (and making the analogous changes on the ui) and leaving this field out of the query when determining the primary phone numbers.

        Attachments

          Activity

          [CRM-7741] selecting primary phone fields via profiles are misleadingly named and configurable
          Donald A. Lobo added a comment -


          Closing issues in batch on 4/16/13 since these issues have not been worked on in a long long time

            People

            • Assignee:
              Donald A. Lobo
              Reporter:
              Aron MEZEI

              Dates

              • Created:
                Updated:
                Resolved: