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 927
    • Issues 927
    • 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
  • #1939

Closed
Open
Opened Aug 09, 2020 by DaveD@DaveDDeveloper

$crazy_null assignment in DB_DataObject has a typo that makes it crazier

https://github.com/civicrm/civicrm-packages/blob/02e7eaa0a2aa072a032afff8179f6c26c1ad87b3/DB/DataObject.php#L4936

strtolower($options['disable_null_strings'] === 'full')

It should be

strtolower($options['disable_null_strings']) === 'full'

Is DB_DataObject still being updated upstream? I can't find a recent repo. Although I don't think this bug ever comes up in practice how it's used in civi.

Edited Aug 10, 2020 by DaveD
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#1939