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

[BUG] Pickup point selection is not remembered fully on the page reload #388

Closed
YachYaroslav opened this issue Aug 7, 2024 · 1 comment

Comments

@YachYaroslav
Copy link

YachYaroslav commented Aug 7, 2024

To Reproduce
Steps to reproduce the behavior:

  1. Go to native Magento checkout.
  2. Fill the address of the Netherlands (e.g. Street Address - Weena XXXX, City - Rotterdam, Zip/Postal Code - 3013AL).
  3. Click on 'PostNL' shipping method and select one of Pickup points.
  4. Refresh the checkout page (F5).
  5. Scroll down to 'PostNL' shipping method.

Expected result
'PostNL' shipping method is selected with 'Pickup' tab being active + previously selected Pickup point is remembered and selected.

Actual result
'PostNL' shipping method is selected, but 'Pickup' tab is not active on the first try (secondly, etc. it's active). When I select 'Pickup' (or if it's selected by the PostNL module), I see a row of the selected pickup marked as active, but the radio input inside the row is not checked itself.

Workaround
None

Screenshots

Before reload:

before-reload

After reload:

after-reload

After reload + click "Next":

after-reload-2

  • Magento version (pure with only tig/postnl-magento2): 2.4.6
  • PHP version: 8.1.3
  • TIG PostNL version: 1.15.2

Also the same issue is reproducible on a highly customized Magento (with Swissup_Firecheckout and many custom modules):

  • Magento version: 2.4.3-p3
  • PHP version: 7.4.28
  • TIG PostNL version: 1.15.2

Magento version 2.4.3-p3 with Swissup_Firecheckout (the same bug):

screenshot-from-another-version

@JorisPostNL
Copy link

JorisPostNL commented Aug 22, 2024

Hi @YachYaroslav, thank you for reporting this issue.

Unfortunately the issue you mention is caused by the way the Magento2 framework itselfs handles the check-out data, and not by our plug-in. We have investigated this issue in the past and came to the conclusion we could not fix this issue without working on Magento2 itself rather than our plug-in. This means that unfortunately there is nothing we can do about this problem at this moment.

Note: since all three issues you posted concern the same root cause I will copy and paste this answer in all three tickets, so it's clear for other visitors what the outcome of your report was.

Kind regards
Joris - PostNL

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants