Magento 2.2.6 Searching for product with dash doesn't work

[Luuk-Meijer]

Preconditions (*)

1. Magento 2 version 2.2.6

Steps to reproduce (*)

1. In "vendor/magento/module-catalog-search/etc/search_request.xml" change

<query xsi:type="boolQuery" name="quick_search_container" boost="1">
    <queryReference clause="should" ref="search" />
    <queryReference clause="must" ref="category"/>
    <queryReference clause="must" ref="price"/>
    <queryReference clause="must" ref="visibility"/>
</query>

to

<query xsi:type="boolQuery" name="quick_search_container" boost="1">
    <queryReference clause="must" ref="search" />
    <queryReference clause="must" ref="category"/>
    <queryReference clause="must" ref="price"/>
    <queryReference clause="must" ref="visibility"/>
</query>

So that the search query "blue boot" only shows products with both the words.
2. Add a product in the back-end with a name with a dash (-) in the name.
For instance "Lakboot Black Mat New A-327 N118" in my case
3. On the frontend search for that product.
So with my example you would search for "A-327".
4. Now when you have the search clause for must nothing is going to show up.

Expected result (*)

1. You would expect the product to show up

Actual result (*)

1. There are no results found

[magento-engcom-team]

Hi @DeLuuk. 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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

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

• yes
• no

[Luuk-Meijer]

@magento-engcom-team I can't reproduce this on a vanilla instance since the "vendor/magento/module-catalog-search/etc/search_request.xml" needs to be changed first.

I know that that would maybe mean it isn't a vanilla bug but in my opinion editing that clause should be possible and should work.

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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-engcom-team 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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• Next steps are available in case you are a member of Community Maintainers.

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

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

HI @DeLuuk thank you for you report, this will fixed by this pr -> #20727

@DeLuuk

After changing any of these options, rebuild your FULLTEXT indexes for the change to take effect. For example, to make two-character words searchable, you could put the following lines in an option file:

[mysqld]
innodb_ft_min_token_size=2
ft_min_word_len=2

https://dev.mysql.com/doc/refman/8.0/en/fulltext-fine-tuning.html

[Luuk-Meijer]

@magento-engcom-team thanks for linking other issue but Im still having trouble.

I want to be able to search for "A-327" not just "A-".
I haven't edited my option file yet, don't even know where that file is, but even if I do I dont think that would fix my problem.

Like I said in the reproduce steps, this isn't just a vanilla Magento 2.2.6 enviroment.

I edited "vendor/magento/module-catalog-search/etc/search_request.xml". If I reverse does changes then it works. But I want to keep those changes since I dont want my search query to work with OR but with AND.

And those changes aren't made in pr -> #20727.

So if I can I'm reopening this since it isn't fixed.

[Luuk-Meijer]

@engcom-backlog-nazar can this issue be opened again?

@DeLuuk i'm will recheck, this must be environmental issue

@DeLuuk yes this is non-issue after i apply changes from pr and set -> #21059 (comment)

[Luuk-Meijer]

@engcom-backlog-nazar but now change:
"vendor/magento/module-catalog-search/etc/search_request.xml" change

<query xsi:type="boolQuery" name="quick_search_container" boost="1">
    <queryReference clause="should" ref="search" />
    <queryReference clause="must" ref="category"/>
    <queryReference clause="must" ref="price"/>
    <queryReference clause="must" ref="visibility"/>
</query>

to

<query xsi:type="boolQuery" name="quick_search_container" boost="1">
    <queryReference clause="must" ref="search" />
    <queryReference clause="must" ref="category"/>
    <queryReference clause="must" ref="price"/>
    <queryReference clause="must" ref="visibility"/>
</query>

And see what happens then

@DeLuuk yes i'm set this :)

[Luuk-Meijer]

@engcom-backlog-nazar oke in that case Im gone try editing that option file.

Where can I find that option file? The url you linked is just for MySql specific, not Magento specific.

I mean I can't put that in a .htaccess or something?