Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 935
    • Issues 935
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Development
  • Core
  • Issues
  • #2076

Closed
Open
Opened Sep 30, 2020 by wouterh@wouterh💬

Standalone event registration confirmation email includes all profile fields

Overview

We see a difference in participant fields between registrations via backend or frontend included in the event confirmation mail.

Reproduction steps

After configuring a particular event with:

  • online registration
  • field of participants in profile
  • confirmation email

Users who register successfully receive the confirmation email with the entry fields included in the email.

frontend-confirmation-email

Up to this point, everything works as it should!

When we want to register participants manually (with confirmation email) via: "Events"> "Register Event Participant" OR via specific event "Event links"> "Register Participant"

The confirmation email contains all existing participant fields, despite them being filled in or having something to do with the profile(s) in the particular event.

backend-confirmation-email

Current behaviour

The confirmation email contains all the existing participant fields, despite them being filled in or having something to do with the profile(s) in the particular event.

Expected behaviour

The confirmation email shouldn't contain all existing participant fields, maybe only filled in participant fields should be included?

Environment information

  • Drupal 8
  • CiviCRM 5.29.1
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dev/core#2076