Skip to content

In-store delivery / Pick in store works when not signed in/ pick in store fails when signed in #39883

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
1 of 5 tasks
echocomm opened this issue May 1, 2025 · 5 comments
Open
1 of 5 tasks
Assignees
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.8 Indicates original Magento version for the Issue report.

Comments

@echocomm
Copy link

echocomm commented May 1, 2025

Preconditions and environment

  • Magento version 2.4.8
  • 1 store
  • signed in customer (my test account) 40miles (64km) from store location

Steps to reproduce

-front end add item to cart and and checkout as GUEST
Pick in store>select store (store shows as designed) (This works as intended, problem is when checkout Signed In)

-front end, SIGN IN and add item to cart. Proceed to checkout after signing in. Pick in store>select store>type address or zip in search field. Hitting enter key in search filed after typing address or zip nothing happens, unless you hit back key to start position (If I type one key stroke in search field and enter back button, store will populate.

Expected result

pick in store>select store for signed in customer should work the same as for a guest

Actual result

Store does not populate when signed in unless back key is entered

Image

Image

to start position.

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 @echocomm. 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.

Copy link

m2-assistant bot commented May 2, 2025

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: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
  • 4. Verify that the issue is reproducible on 2.4-develop branch
    Details- 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-November engcom-November added the Reported on 2.4.8 Indicates original Magento version for the Issue report. label May 2, 2025
@engcom-November
Copy link
Contributor

Hello @echocomm ,

Thank you for your report and collaboration.

We attempted to reproduce the issue in our latest version 2.4.8 but were unable to reproduce it. Please find the attached screenshot for reference.

In-Store-SIGN.IN.mov

Steps to Reproduce:

  • Visit the storefront (try for as a guest and Logged user as well )
  • Add any item to the cart
  • Proceed to checkout
  • Select "Pick In Store"
  • Type an address or zip code in the store locator search field and press Enter
  • Store populates correctly and can be selected

We followed these steps and did not encounter any issues. Could you please recheck in the latest version of Magento and let us know if we are missing any steps to reproduce this issue?

Therefore, we are marking this ticket as "Issue: Needs Update".

Thank you!

@engcom-November engcom-November added the Issue: needs update Additional information is require, waiting for response label May 7, 2025
@ct-prd-projects-boards-automation ct-prd-projects-boards-automation bot moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board May 7, 2025
@echocomm
Copy link
Author

echocomm commented May 8, 2025 via email

@engcom-November
Copy link
Contributor

Hello @echocomm ,

To assist further, could you please share additional details about your setup, such as:

Operating System and version

MySQL version

PHP version

Web server (e.g., Apache, Nginx) and version

Any other relevant configurations or customizations

This information will help us better understand and find the root cause of the issue.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.8 Indicates original Magento version for the Issue report.
Projects
Development

No branches or pull requests

2 participants