Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-15956

Report section headers triggered by capitalization differences

    Details

    • Type: Bug
    • Status: Done/Fixed
    • Priority: Trivial
    • Resolution: Fixed/Completed
    • Affects Version/s: 4.4.11, 4.5.6, 4.6
    • Fix Version/s: None
    • Component/s: CiviReport
    • Labels:
    • Documentation Required?:
      None

      Description

      When a report orders by a value and has section headers, the ORDER BY in MySQL brings the sections together, but the headers are simply triggered by a change in the ordered-by field's value. A smarty function evaluates whether the value has changed, but it is case-sensitive, unlike the ordering in the query result which is case-insensitive.

      The outcome of this is that you'd have a query result like:
      Warrenton ...
      Warrenton ...
      Washington ...
      Washington ...
      WASHINGTON ...
      Washington ...

      becoming rendered like

      Warrenton______
      Warrenton ...
      Warrenton ...

      Washington______
      Washington ...
      Washington ...

      WASHINGTON______
      WASHINGTON ...

      Washington______
      Washington ...

      The smarty function needs to be case-insensitive.

        Attachments

          Activity

            People

            • Assignee:
              colemanw Coleman Watts
              Reporter:
              andrewhunt Andrew Hunt
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: