Warning when Search Terms page is opened by clicking option at the footer

Preconditions (*)

1. Fresh Magento installation with magento 2.3-develop

Steps to reproduce (*)

1. Setup vanilla 2.3-develop
2. Create a product in the backend, give it the name "test"
3. On the frontend, perform a search query, search for "test"
4. Notice that it finds the product
5. If you now go to the Search Terms page in the frontend, it will show the search term "test" => good
6. Now in the backend, go to Marketing > SEO & Search > Search Terms
7. Open your "test" term
8. Set the "Number of Uses" to 0 and save
9. Click On Search terms option present at the bottom

Expected result (*)

1. Page opens without any error
2. There is no errors in the system log

Actual result (*)

1. In developer Magento mode Warning is shown on the Search Terms page
   Warning: natcasesort() expects parameter 1 to be array, null given in /var/www/html/deployer/instances/i-25245-2-3-develop/app/code/Magento/Search/Block/Term.php on line 102 [] []
2. In default mode error is shown in system.log

Additional information

Based on comment #25245 (comment)
Fix seems to be very easy:

diff --git a/app/code/Magento/Search/Block/Term.php b/app/code/Magento/Search/Block/Term.php
index b27ef6b01fd..a1eb0bb64c9 100644
--- a/app/code/Magento/Search/Block/Term.php
+++ b/app/code/Magento/Search/Block/Term.php
@@ -87,6 +87,7 @@ class Term extends Template
                 return $this;
             }

+            $termKeys = [];
             $this->_maxPopularity = reset($terms)->getPopularity();
             $this->_minPopularity = end($terms)->getPopularity();
             $range = $this->_maxPopularity - $this->_minPopularity;

[m2-assistant]

Hi @vishalverma279. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@vishalverma279 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

@magento give me 2.3-develop instance

[m2-assistant]

Hi @vishalverma279. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @krishprakash. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[krishprakash]

@magento give me 2.3-develop instance

[magento-engcom-team]

Hi @krishprakash. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @krishprakash, here is your Magento instance.
Admin access: https://i-25245-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[krishprakash]

Hi @vishalverma279. Thank you for your report.
Not able to reproduce this issue as provided steps by you.
Please provide more details and confirm that issue is reproduced on venilla magento instance.
Thanks

@krishprakash possibly warnigs are disabled at the docker instance of magento. can you please check by cloning the same at your locals server
https://drive.google.com/file/d/1rysG1boY1TobKhajeuHoBK5IgoL47zXL/view

[krishprakash]

@vishalverma279. checked at local 2.3-develop and 2.3.3 instances but could not reproduce this issue.
https://www.screencast.com/t/MHbrrq3Chd

[krishprakash]

Hi @vishalverma279 feel free to reopen the if you confirm that issue is reproduced on venilla magento instance.
Thanks