Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C CiviDiscount
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 34
    • Issues 34
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Extensions
  • CiviDiscount
  • Issues
  • #74

Using Pricesets for memberships causes Discount Tracking to fail.

Created by: generalredneck

The following is not using any Priceset, but instead what you would find on the Contribution page Membership Section. No Pricest

This is using a priceset: Priceset

Notice that in this one, $membership_type is an array. This is because you can select more than one. With that said, how is usage going to be tracked on multiple memberships? Should it be per membership or per invoice. In this case I still only have 1 membership but could easily have 2 or 3. For now I'm going to create A PR that fixes it where if you have any of the memberships, it creates only one record.

This is an issue in 2.5 as well as master. See https://github.com/dlobo/org.civicrm.module.cividiscount/blob/master/cividiscount.php#L624

Assignee
Assign to
Time tracking