Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C CiviCRM Core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,376
    • Issues 1,376
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • CiviCRM Core
  • Issues
  • #2878

Closed
Open
Created Sep 30, 2021 by magnolia61@magnolia61

Custom Date Tokens do not resolve if the field has no time part

Overview

Custom Date Tokens do not resolve if the field has no time part

Reproduction steps

  1. apply https://github.com/civicrm/civicrm-core/pull/21666 to support participant tokens
  2. send a scheduled reminder with a date field and some other tokens

Current behaviour

The date field does not resolve, but not only that. It caused no token at all to render.

Expected behaviour

A rendered date field would be expected of the custom date field token.

Environment information

Current master (5.43) with https://github.com/civicrm/civicrm-core/pull/21666

Comments

When in the backend I change the date field to also have a time part, the token starts rendering.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking