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 913
    • Issues 913
    • 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
  • #1040

Closed
Open
Opened Jun 13, 2019 by Andrew Hunt@andrewhuntDeveloper

Inconsistent validation of price field and option visibility combinations

See https://github.com/civicrm/civicrm-core/pull/13966 for early discussion. Basically, CiviCRM occasionally attempts to prevent you from creating a price field with Admin visibility that only has options with Public visibility or vice-versa. It is by no means consistent or effective in stopping this, however.

Some people hold the opinion that there should be no validation on this. At the very least, the validation should allow you to fix situations where there is no price option with visibility that matches its field's visibility (the situation that PR 13966 fixes).

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