CRM-9117 Participant 1 name showing as billing name on multiple participant registrations

    Details

    • Type: Bug
    • Status: Done/Fixed
    • Priority: Trivial
    • Resolution: Fixed/Completed
    • Affects Version/s: 4.0.6
    • Fix Version/s: 4.1.0
    • Component/s: CiviEvent
    • Labels:
      None

      Description

      On the confirmation page, thank you page, and confirmation email. Should show the participant's name rather than the billing name, which might be different. Looks like it's assigned incorrectly to the smarty $part variable.

        Attachments

          Activity

          [CRM-9117] Participant 1 name showing as billing name on multiple participant registrations
          Yashodha Chaku added a comment -

          I couldn't replicate the same on my local machine, worked fine
          Could you replicate the above on our demo (http://demo.civicrm.org/)

          Donald A. Lobo added a comment -

          Jay:

          can u let us know where u think the incorrect assignment is

          Jason McGraw added a comment -

          Replicated on the demo using Multiple Participants Registration Test.

          Went to online registration.
          Chose to register 2 participants
          Under new individual, entered first name as "Jane", last name as "Smith"
          Under billing name and address, entered first name as "John", last name as "Doe"
          Under second participant new individual, entered first name as "Bob", last name as "Franklin"
          Went to confirmation page and it shows under Conference Fee:
          Participant 1: John Doe
          Participant 2: Bob Franklin

          Participant 1 should be Jane Smith

          Will gladly send over a confirmation screenshot.

          Rohan S. Chavan added a comment -

          Tested in r37476

            People

            • Assignee:
              Rohan S. Chavan
              Reporter:
              Jason McGraw

              Dates

              • Created:
                Updated:
                Resolved: