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 932
    • Issues 932
    • 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
  • #408

Closed
Open
Opened Sep 25, 2018 by ddoligalski@ddoligalski

priority_id getting set incorrectly

A modification in CRM/Member/BAO/Membership.php made in 4.7.20 is causing a db constraint error when attempting to make payment on a membership. (See https://github.com/civicrm/civicrm-core/commit/66a1e31f279137676e395ce60eda2cc14bcde5f1#diff-f43c8498e32f5b2d68ab27bcd243ca36)

The specific modification (in multiple places) is to set the value of 'priority_id' to 'Normal'. It previously was set to 2. My guess is that 'Normal' should be looked up in option_values with the value saved to priority_id.

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#408