Skip to content

Order customer_email LIKE % condition doesn't work because of the Core Magneto Framework issue #39878

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

Open
5 tasks
Genaker opened this issue May 1, 2025 · 3 comments
Labels
Issue: ready for confirmation Reported on 2.4.x Indicates original Magento version for the Issue report. Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it

Comments

@Genaker
Copy link

Genaker commented May 1, 2025

Preconditions and environment

  • Magento version: all

  • Anything else that would help a developer reproduce the bug

          /* @var $collection AbstractCollection */ in my case order grid collection 
    

Magento\Sales\Model\ResourceModel\Order\Grid\Collection</
$collection->addFieldToFilter($field, ['LIKE' => $value . '%']);

/var/www/html/magento/vendor/magento/module-sales/Model/ResourceModel/Order/Grid/Collection.php

result is:

Image

if make like this :
$collection->addFieldToFilter($field, ['like' => $value . '%']);

it works. You need lower case if you are doing some stuff

it comes from the Zend ok but after some broken magneto code make from it not like but =

Image

i was too tired to test why magento is broken.

please check

Steps to reproduce

test

Expected result

like works

Actual result

like doesn't work

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”.
Copy link

m2-assistant bot commented May 1, 2025

Hi @Genaker. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.


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.

@Genaker
Copy link
Author

Genaker commented May 1, 2025

PR created: #39879

@engcom-Bravo engcom-Bravo added Reported on 2.4.x Indicates original Magento version for the Issue report. Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it labels May 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: ready for confirmation Reported on 2.4.x Indicates original Magento version for the Issue report. Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Projects
Status: Ready for Confirmation
Development

No branches or pull requests

2 participants