magento 2 plus search event observer not getting the same data as store front end.

[Sanjay-100]

Preconditions and environment

• Magento versions 2.3 and 2.4
• Anything else that would help a developer reproduce the bug
  I create the custom modules I want all search results the same as storefronts. here you can find the code https://github.com/Sanjay-100/magento2_search

Steps to reproduce

1 Setup mangeto
2 https://github.com/Sanjay-100/magento2_search install this module
3 do store search
4 plugin show the search result was different you can compare with without plugin and with plugin, code see both result are too different

Expected result

do the store search the store search results will be output into modules event observer

Actual result

do the store search the store search results will be output into modules event observer

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @Sanjay-100. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

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

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

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

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

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

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[Sanjay-100]

@m2-community-project

Summary of the issue :- Magento versions 2.3 and 2.4
Anything else that would help a developer reproduce the bug
I create the custom modules I want all search results the same as storefronts. here you can find the code https://github.com/Sanjay-100/magento2_search

Information on your environment :- LEMP stack magento 2.4 development mode
Steps to reproduce :- user the my git repo test Magento modules and compare with Magento default search
Expected and actual results :- on my code repo result same as the magento

[m2-assistant]

Hi @engcom-Hotel. 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.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!

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

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

[engcom-Hotel]

Hello @Sanjay-100,

Thanks for the report and contribution!

We request you to please provide some more information on this issue like expected and the actual result with a screenshot if possible. Currently, both actual and expected results are the same.

Also please let us know the specific issue you are facing while using Magento. I will also suggest you to please raise this query in Magento stack exchange.

Thanks

[engcom-Hotel]

Dear @Sanjay-100,

We have noticed that this issue has not been updated for a period of 14 Days. Hence we assume that this issue is fixed now, so we are closing it. Please raise a fresh ticket or reopen this ticket if you need more assistance on this.

Regards