Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dev/core#553: Creating new event takes value from default value not from saved template for custom fields #14480

Merged
merged 1 commit into from
Jun 21, 2019

Conversation

monishdeb
Copy link
Member

Overview

When creating a new event using a template the new event screen is taking the default values directly from the custom fields, and not from what's saved in the event template.

Steps to replicate:

  1. Create a custom field for Events
  2. Set default value say 'abc' for that custom field
  3. Create/Edit an event template and save with custom field value say 'def'
  4. Now create a new event using that event template

Issue - Custom field is set to default value 'abc' instead of 'def'

Before

before

After

after

@civibot
Copy link

civibot bot commented Jun 7, 2019

(Standard links)

@civibot civibot bot added the master label Jun 7, 2019
@scoobird
Copy link
Contributor

Tested this, and it works as expected. Thanks!

@colemanw
Copy link
Member

I've checked the code. Merging based on review and passing tests.

@colemanw colemanw merged commit 7bfd05f into civicrm:master Jun 21, 2019
@monishdeb monishdeb deleted the core-553 branch July 2, 2019 12:42
@jusfreeman
Copy link
Contributor

This change possibly introduced a regression bug, see https://lab.civicrm.org/dev/core/issues/1241#note_23222

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants