Navigation Menu

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

Core/dev#692 : Support search arguments to Case Search form #15370

Merged
merged 1 commit into from Oct 26, 2019

Conversation

monishdeb
Copy link
Member

Overview

This PR extends the fix and make all possible mailing search filters to be used as a url arguments on forced search using 'Find Mailing' or 'Advance Search'

Before

Search arguments didn't work
Screen Shot 2019-10-01 at 6 23 16 PM

After

Search arguments works:
Screen Shot 2019-10-01 at 6 40 21 PM

@civibot
Copy link

civibot bot commented Oct 1, 2019

(Standard links)

@civibot civibot bot added the master label Oct 1, 2019
@demeritcowboy
Copy link
Contributor

@monishdeb Does the search function return the right results for you when using url params? I tried it on the test site here with the exact same url arguments as in the screenshot (civicrm/case/search?reset=1&case_type_id=1&force=1) and it does fill in the search form, but then returns all results not just the ones with the requested case type. Also tried case_subject and it does the same thing.

Also, when searching for subject normally on the form not using url params, I get a warning here that I don't see on dmaster: Notice: Array to string conversion in CRM_Core_I18n->strarg() (line 292 of /home/jenkins/bknix-dfl/build/core-15370-8rvom/web/sites/all/modules/civicrm/CRM/Core/I18n.php)

@eileenmcnaughton
Copy link
Contributor

I think there are a couple more things that need to be done

  1. fix the handling post-save per @demeritcowboy
  2. convert the dates to use datepicker & don't add them separately
  3. fix the notice on qill handling

I think this is mergable once 3 is fixed as that is a regression - the other 2 can follow as this is a code tidy up. The notice is coming out of the qill - I put up a separate PR here #15373 that extracts various functions used on the contribution search that would ideally be reused to help you here

@eileenmcnaughton
Copy link
Contributor

eileenmcnaughton commented Oct 2, 2019

Specifically https://github.com/civicrm/civicrm-core/pull/15373/files#diff-ca3790966db8d584af7de8f6c6b7abfbR157 should handle the qill thing

Opps - now removed that to break it up - above is out of date

@eileenmcnaughton
Copy link
Contributor

eileenmcnaughton added a commit to eileenmcnaughton/civicrm-core that referenced this pull request Oct 3, 2019
This consolidates 2 places where formValues are determined on contribution search. In one place
force is handled in the other retrieving from the form is handled. It seems Ok to handle both in
one place & call that. This might help iron on some glitches Monish is hitting on civicrm#15370

We should probably add saved search retrieval in too

To confirm this works use this url
civicrm/contribute/search?reset=1&reset=1&sort_name=p&receive_date_high=20180101&force=1

- it should filter. If you add another criteria to the form afterwards the url criteria should
be present on the form from the url & the new one should also be respected. If you actively remove the url
criteria on the form it is ignored in the search
eileenmcnaughton added a commit to eileenmcnaughton/civicrm-core that referenced this pull request Oct 4, 2019
This consolidates 2 places where formValues are determined on contribution search. In one place
force is handled in the other retrieving from the form is handled. It seems Ok to handle both in
one place & call that. This might help iron on some glitches Monish is hitting on civicrm#15370

We should probably add saved search retrieval in too

To confirm this works use this url
civicrm/contribute/search?reset=1&reset=1&sort_name=p&receive_date_high=20180101&force=1

- it should filter. If you add another criteria to the form afterwards the url criteria should
be present on the form from the url & the new one should also be respected. If you actively remove the url
criteria on the form it is ignored in the search
demeritcowboy pushed a commit to demeritcowboy/civicrm-core that referenced this pull request Oct 4, 2019
This consolidates 2 places where formValues are determined on contribution search. In one place
force is handled in the other retrieving from the form is handled. It seems Ok to handle both in
one place & call that. This might help iron on some glitches Monish is hitting on civicrm#15370

We should probably add saved search retrieval in too

To confirm this works use this url
civicrm/contribute/search?reset=1&reset=1&sort_name=p&receive_date_high=20180101&force=1

- it should filter. If you add another criteria to the form afterwards the url criteria should
be present on the form from the url & the new one should also be respected. If you actively remove the url
criteria on the form it is ignored in the search
magnolia61 pushed a commit to magnolia61/civicrm-core that referenced this pull request Oct 13, 2019
This consolidates 2 places where formValues are determined on contribution search. In one place
force is handled in the other retrieving from the form is handled. It seems Ok to handle both in
one place & call that. This might help iron on some glitches Monish is hitting on civicrm#15370

We should probably add saved search retrieval in too

To confirm this works use this url
civicrm/contribute/search?reset=1&reset=1&sort_name=p&receive_date_high=20180101&force=1

- it should filter. If you add another criteria to the form afterwards the url criteria should
be present on the form from the url & the new one should also be respected. If you actively remove the url
criteria on the form it is ignored in the search
@eileenmcnaughton
Copy link
Contributor

merging this - per discussion #15614 will make sure the previous blocker (3 above) is fixed post merge

@eileenmcnaughton eileenmcnaughton merged commit 1d5d009 into civicrm:master Oct 26, 2019
@monishdeb monishdeb deleted the core-692-2 branch October 28, 2019 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
3 participants