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/issues/636 - Custom field for Address: The "No" value is not defaulted #13397

Merged
merged 1 commit into from
Jan 6, 2019

Conversation

pradpnayak
Copy link
Contributor

@pradpnayak pradpnayak commented Jan 4, 2019

Overview

https://lab.civicrm.org/dev/core/issues/636

Before

address custom field

After

address custom field-after

Technical Details

If the value is set to 0 or FALSE !empty() will return FALSE, but isset() will return TRUE. Hence using isset() to check if the variable has not empty value.

@civibot
Copy link

civibot bot commented Jan 4, 2019

(Standard links)

@civibot civibot bot added the master label Jan 4, 2019
@pradpnayak pradpnayak changed the title dev/core/issues/636 - Check if value is isset rather empty dev/core/issues/636 - Custom field for Address: The "No" value is not defaulted Jan 4, 2019
@mattwire
Copy link
Contributor

mattwire commented Jan 6, 2019

Tested and confirmed this fixes the issue. Please can you merge @yashodha @monishdeb ?

@pradpnayak
Copy link
Contributor Author

Thanks @mattwire !

@seamuslee001
Copy link
Contributor

Merging as per Matt's Review

@seamuslee001 seamuslee001 merged commit 827c534 into civicrm:master Jan 6, 2019
@pradpnayak pradpnayak deleted the AddressCustomFieldFix branch January 17, 2019 01:22
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.

3 participants