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

Fulltext search does not work with multiselect attribute option values #13972

Closed
superdav42 opened this issue Mar 6, 2018 · 7 comments
Closed
Labels
Component: CatalogSearch Priority: P3 May be fixed according to the position in the backlog. Progress: done Reported on 2.2.x Indicates original Magento version for the Issue report. Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. stale issue

Comments

@superdav42
Copy link

superdav42 commented Mar 6, 2018

Description

Create a custom product attribute with the multiselect input type. Create several options. Make the attribute searchable and shown in advanced search.
Create product with the attribute and select several values.

Preconditions

  1. Occurs with Magento 2.2.3 and any 2.2.x

Steps to reproduce

  1. From Admin, Go to Stores - Attribute Product. Click Add New Product
  2. From Catalog Input Type for Store Owner select Multiple Select
  3. Add several Options under Manage Options(Values of Your Attribute)
  4. From left ATTRIBUTE INFORMATION select Storefront Properties
  5. Select Use in Search - Yes, Visible in Advanced Search - Yes. Save Attribute
    search
  6. Go to Catalog - Products and Add Product
  7. Click Add Attribute and add the previously created attribute
  8. Under Attributes select all available options (use ctrl key) and Save the product
  9. Open Storefront, click Advanced Search
    advanced
  10. Select an Option or several options from Custom Product Attribute and click Search
    cpa search

Expected result

  1. Searching by label name should be possible in the quick search or advanced search to find the associated product.

Actual result

  1. Nothing is found
    search_result

I just opened this issue because my PR to fix it hasn't got any attention yet. #13001

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Mar 6, 2018
@magento-engcom-team magento-engcom-team added the Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed label Mar 7, 2018
@magento-engcom-team
Copy link
Contributor

@superdav42, thank you for your report.
We've acknowledged the issue and added to our backlog.

@magento-engcom-team magento-engcom-team added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Mar 7, 2018
@nkajic
Copy link
Member

nkajic commented Oct 4, 2018

This is documentation problem.

Multiselect attributes needs to have "Visible in Advanced Search" flag checked in addition to "Use in Search" and "Search Weight" mentioned in documentation.

After this do reindex.

Please see implementation on

&& ($attribute->getIsVisibleInAdvancedSearch()

@ghost
Copy link

ghost commented Mar 1, 2019

@nkajic how can I add these options to my attribute that I am creating programmatically? and where is the official documentation on attribute options?

@engcom-Bravo engcom-Bravo self-assigned this Jan 6, 2020
@m2-assistant
Copy link

m2-assistant bot commented Jan 6, 2020

Hi @engcom-Bravo. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

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

  • 2. Verify that the issue is reproducible on 2.4-develop branch

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

  • 3. If the issue is not relevant or is not reproducible any more, feel free to close it.


@engcom-Bravo engcom-Bravo added Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Component: CatalogSearch Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed and removed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Jan 6, 2020
@ghost ghost unassigned engcom-Bravo Jan 6, 2020
@magento-engcom-team
Copy link
Contributor

✅ Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-30223 were created

Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

@matthew99
Copy link

If it is any help this is my experience.
I use Mirasvit Elasticsearch module. In Mirasvit I can add a search index for any attribute (in my case 'writers'), which is a great feature.

My experience:
Only first value of multiselect could be found by advanced search and layered nav.
There is difference between /catalogsearch/results, advanced search and layered nav.

In my case I made an multi select attribute 'writers' (values writer1, writer2, writer3) .
Product 'Book1' has writer1, writer2, writer3 set in the write multiselect attribute.

When I search for 'writ' in the search box, the Miravit search autocomplete neatly lists the 3 writers and the book in seperate blocks. Clicking on any writer leads to advanced search &author=x, which means no results - EXCEPT for the first value (writer1).

If I search for 'writ' and hit enter (/calalogsearch/results/) it lists Book1 and the 3 writers. However, in the layered nav only writer1 is found. Mirasvit overrides this catalog/search but lists all three writers here as well. Clicking same result (-> advanced search only works for first writer).

If I pick advanced search:
Advanced searching on writer 2 or 3 does not list my book.
Advanced searching on writer 1 list my book.

If I click on the category with Book1 in it, in the layered navigation only Writer1 is listed - again, first value.

@ghost ghost removed Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development labels Oct 20, 2020
@sdzhepa sdzhepa added the Reported on 2.2.x Indicates original Magento version for the Issue report. label Nov 30, 2020
@sivaschenko sivaschenko removed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch labels Dec 3, 2020
@sivaschenko sivaschenko added Priority: P3 May be fixed according to the position in the backlog. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. and removed Issue: ready for confirmation labels Dec 3, 2020
@stale
Copy link

stale bot commented Feb 17, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 14 days if no further activity occurs. Is this issue still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? Thank you for your contributions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: CatalogSearch Priority: P3 May be fixed according to the position in the backlog. Progress: done Reported on 2.2.x Indicates original Magento version for the Issue report. Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. stale issue
Projects
None yet
Development

No branches or pull requests

7 participants