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#696) Changes to copied event phone and email reflects in or… #13534

Merged
merged 1 commit into from
Feb 19, 2019

Conversation

yashodha
Copy link
Contributor

@yashodha yashodha commented Feb 5, 2019

…iginal event phone and email

Overview

Steps to replicate:

  1. Create an event X with location A, including email A and phone A
  2. Create copy of event X say Y and go to location tab for event Y (which will now show location A).
  3. Click Create new location radio and then click new location B, including email B and phone B.
  4. Check event X - email B and phone B will be listed

Before

Event X has phone and email updated to B

After

Event Y has phone and email updated to B which is the desired behavior.

@civibot
Copy link

civibot bot commented Feb 5, 2019

(Standard links)

@civibot civibot bot added the master label Feb 5, 2019
@yashodha
Copy link
Contributor Author

yashodha commented Feb 5, 2019

@lcdservices

Can you please test this? This is similar to erroneous behavior for event addresses that you had reported a while back.

@eileenmcnaughton
Copy link
Contributor

Just a quick comment per my note on the gitlab - my vague recollection is the 'eroneous' behaviour was something that DGG did by design - as I recall the idea was that if a location changed it was good to be able to edit all at once. However, if others weigh in that would override my recollection :-)

@yashodha
Copy link
Contributor Author

yashodha commented Feb 7, 2019

@eileenmcnaughton
I don't recollect this being a feature, though it certainly stuck out like a bug to me :). We had a similar bug with address (reported by a few users) which was fixed for
https://lab.civicrm.org/dev/core/issues/108
https://lab.civicrm.org/dev/core/issues/255

@lcdservices
Copy link
Contributor

@yashodha I've tested and confirmed this works as expected.
@eileenmcnaughton I agree with the change. If a person is intentionally choosing to create a new location, that should affect the email and phone as well -- they should not remain tied to the original location. Otherwise there is no way to disconnect the email/phone from the initial event when creating a copy.

@eileenmcnaughton eileenmcnaughton added the merge ready PR will be merged after a few days if there are no objections label Feb 16, 2019
@eileenmcnaughton
Copy link
Contributor

@lcdservices OK - thanks - added merge-ready then - I'll leave a few days more & if no comments we can merge

@eileenmcnaughton eileenmcnaughton merged commit e9a6669 into civicrm:master Feb 19, 2019
@yashodha
Copy link
Contributor Author

@lcdservices @eileenmcnaughton thanks!

@eileenmcnaughton
Copy link
Contributor

@yashodha I think anyone else who wanted to weigh in on this had a chance since I emailed the dev list so @lcdservices's input carries the day!

@yashodha yashodha deleted the dev-696 branch April 30, 2019 16:06
@jitendrapurohit
Copy link
Contributor

Seems this change affects the storage of email and phone fields? Related gitlab - https://lab.civicrm.org/dev/core/-/issues/1973 @yashodha @eileenmcnaughton

@eileenmcnaughton
Copy link
Contributor

ug - @yashodha will you have a chance to look?

@eileenmcnaughton
Copy link
Contributor

I think this addresses the regression without breaking your fix @yashodha

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
master merge ready PR will be merged after a few days if there are no objections
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants