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
  • #1175

Closed
Open
Opened Aug 09, 2019 by JonGold@JonGoldDeveloper

Regression: Custom searches no longer work

Introduced by this commit. It's a pretty common-sense cleanup to not pass a null array when it's an optional parameter defaulted to NULL. However, in one of the methods, CRM_Core_DAO::composeQuery the parameter wasn't defined as optional.

If one looks at that commit and looks at this one, this should be a fairly easy fix to review.

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