magento2 icon indicating copy to clipboard operation
magento2 copied to clipboard

Deprecated Functionality: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /var/www/vendor/magento/framework/DataObject.php on line 131

Open bmxmale opened this issue 2 years ago • 2 comments

Preconditions and environment

  • CE 2.4.4
  • PHP8.1

Steps to reproduce

Issue related with #35602, same steps, desc copied from related issue.

Enable product alert stock in BO (Configuration > Catalog >Product Alerts > Allow Alert When Product Comes Back in Stock > Yes, Allow Alert When Product Price Changes - Yes) Reindex and cache flush Front end - Login as customer - Select a Product without stock - Register to a product stock alert (Notify me when the price drops, Notify me when this product is in stock) Add stock to that product from admin Launch consumers

Expected result

Alert stock email being sent

Actual result

Emails not triggered for Product Alerts

If we have configured error email, we will receive error:

Product alerts cron warnings

Deprecated Functionality: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /var/www/vendor/magento/framework/DataObject.php on line 131```

Changes from https://github.com/magento/magento2/commit/0e9b5434ea89792bae7118894ce0a412e08b2cd7 on DataObject not helping.

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

bmxmale avatar Sep 23 '22 22:09 bmxmale

Hi @bmxmale. 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.


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

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: 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.

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

m2-assistant[bot] avatar Sep 23 '22 22:09 m2-assistant[bot]

Related with https://github.com/magento/magento2/issues/35602

bmxmale avatar Sep 23 '22 22:09 bmxmale

Hi @engcom-November. 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: :point_down:

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

    DetailsIf 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.

m2-assistant[bot] avatar Sep 26 '22 06:09 m2-assistant[bot]

Hi @bmxmale , Thank you for reporting and collaboration. Product Alert emails are not getting triggered on Magento 2.4-develop instance is an ongoing issue confirmed https://github.com/magento/magento2/issues/35602. Its recommended to track same issue in a single bug only. We are closing this issue as duplicate. Kindly move on to this https://github.com/magento/magento2/issues/35602 for latest updates / solutions on the same. Thank you.

engcom-November avatar Sep 26 '22 06:09 engcom-November