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

[REF] Standardise form handling in the Find Pledges search form #15930

Merged
merged 1 commit into from
Nov 23, 2019

Conversation

seamuslee001
Copy link
Contributor

Overview

This standardises the form handling in the Find Pledges search form

Before

Transient style of handling form values

After

consolidated function to handle form values

ping @eileenmcnaughton @demeritcowboy

@civibot
Copy link

civibot bot commented Nov 22, 2019

(Standard links)

@civibot civibot bot added the master label Nov 22, 2019
@demeritcowboy
Copy link
Contributor

demeritcowboy commented Nov 23, 2019

Did an r-run and looks ok just a few things not sure if they're expected to work in urls with force=1?

  • Contact-related fields, e.g. the sort_name field works, but not contact_tags or contact_type.
  • pledge_acknowledge_date_is_not_null doesn't seem to work (the one at the bottom of the form about acknowledgement sent). I also tried it using CIVICRM_QFID_1_pledge_acknowledge_date_is_not_null.

But they all work fine using the form itself.

@seamuslee001
Copy link
Contributor Author

@demeritcowboy certainly the latter hasn't been converted to metadata and the former i don't believe the other fields have been added yet for metadata apart from sort_name

@seamuslee001
Copy link
Contributor Author

Test fail is unrelated and i'm going to merge this based on @demeritcowboy 's testing

@seamuslee001 seamuslee001 merged commit 3201a1f into civicrm:master Nov 23, 2019
@seamuslee001 seamuslee001 deleted the standardise_pledge_search branch November 23, 2019 23:37
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.

2 participants