CRM-15191 Token selector includes disabled fields

    Details

    • Type: Bug
    • Status: Done/Fixed
    • Priority: Trivial
    • Resolution: Fixed/Completed
    • Affects Version/s: 4.5
    • Fix Version/s: 4.5
    • Component/s: None
    • Labels:
      None
    • Documentation Required?:
      None

      Description

      This affects the new token selector in 4.5, and probably the old one in 4.4 also. Disabled fields and disabled sets all display in token selector.

        Attachments

          Activity

          [CRM-15191] Token selector includes disabled fields
          Coleman Watts added a comment -

          I'll see if it's a quick fix for 4.5 otherwise I'll push it to a future version.

          Coleman Watts added a comment -

          Ok root of the problem is actually a caching issue: api.setvalue doesn't properly clear the custom field cache.

          And another problem when I solved that one: disabled fields show up as blank tokens in the list.

          Coleman Watts added a comment -

          https://github.com/civicrm/civicrm-core/pull/3969

          Caching issue could have led to all sorts of quirky bug reports so I'm glad I caught it.

            People

            • Assignee:
              David Greenberg
              Reporter:
              Coleman Watts

              Dates

              • Created:
                Updated:
                Resolved: