Answers.Body: <p>I could replicate this issue on my local machine, this seems to be a core bug and have logged issue at <a href="https://lab.civicrm.org/dev/core/issues/353" rel="nofollow noreferrer">https://lab.civicrm.org/dev/core/issues/353</a>.</p>
  
  <p>I think the search does provide results when we disable record type options
  <a href="https://i.sstatic.net/mEThi.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/mEThi.png" alt="enter image description here"></a></p>
  
  <p>So in the mean time until the bug gets fixed you can rely on this option (hope it shoes correct count of results ;))</p>
  
  <p>I have also submitted PR for this at <a href="https://github.com/civicrm/civicrm-core/pull/12713" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-core/pull/12713</a> if you can please try after applying patch and then comment on PR about your QA that would help to speedup the process of merging the code in next release.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-22T11:26:05.220Z
Answers.Text: Wim can please try the patch if it works for you? And also can this post marked as answered if it solves your problem?
Answers.UserDisplayName: Pradeep Nayak
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-22T14:06:58.127Z
Answers.Text: @PradeepNayak stack exchange etiquette is generally to allow 24h or so before accepting so other people aren't discouraged from answering, at least at first.
Answers.UserDisplayName: mbrig
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-22T14:52:26.137Z
Answers.Text: It seems the fix is working fine - thanks Pradeep for the quick reply. I'll leave this post open for a while to see if anyone else has additional comments :-)
Answers.UserDisplayName: Wim van Meurs
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-28T08:34:53.623Z
Answers.Text: Marked as Answered
Answers.UserDisplayName: Wim van Meurs
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-22T10:57:00.643Z
Answers.LastActivityDate: 2018-08-22T11:25:18.003Z
Answers.LastEditDate: 2018-08-22T11:25:18.003Z
Answers.UserDisplayName: Pradeep Nayak
Body: <p>We just upgraded our CiviCRM sites to 5.4.0 and found out that Search | Activity Search always leads to an empty result set. We're on Joomla 3.8.11 but I see the same result on the demo civicrm sandbox (which is running 5.6 alpha 1 on Drupal). Activities are still in place - they show up on contact pages and in the search builder. Is there a change in functionality on the Activity Search page that we're not aware of or is this a bug? Anyone able to confirm? </p>
  
Tags: <activities>
Title: As of 5.4.0, Activity Search gives an empty result set - patch is available
ThreadText: # As of 5.4.0, Activity Search gives an empty result set - patch is available
  
  (Asked by: username_0 on 2018-08-22)
  
  We just upgraded our CiviCRM sites to 5.4.0 and found out that Search | Activity Search always leads to an empty result set. We're on Joomla 3.8.11 but I see the same result on the demo civicrm sandbox (which is running 5.6 alpha 1 on Drupal). Activities are still in place - they show up on contact pages and in the search builder. Is there a change in functionality on the Activity Search page that we're not aware of or is this a bug? Anyone able to confirm?
  
  **Tags:** activities
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-08-22. Score: 3 | Accepted answer
  
  I could replicate this issue on my local machine, this seems to be a core bug and have logged issue at <https://lab.civicrm.org/dev/core/issues/353>.
  
  I think the search does provide results when we disable record type options
  [![enter image description here](https://i.sstatic.net/mEThi.png)](https://i.sstatic.net/mEThi.png)
  
  So in the mean time until the bug gets fixed you can rely on this option (hope it shoes correct count of results ;))
  
  I have also submitted PR for this at <https://github.com/civicrm/civicrm-core/pull/12713> if you can please try after applying patch and then comment on PR about your QA that would help to speedup the process of merging the code in next release.
  
  > **Comments:**
  > **username_1**: Wim can please try the patch if it works for you? And also can this post marked as answered if it solves your problem?  
  > **username_2**: @PradeepNayak stack exchange etiquette is generally to allow 24h or so before accepting so other people aren't discouraged from answering, at least at first.  
  > **username_0**: It seems the fix is working fine - thanks Pradeep for the quick reply. I'll leave this post open for a while to see if anyone else has additional comments :-)  
  > **username_0**: Marked as Answered  
  
  ---
  
  