You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
clotairer opened this issue
Apr 30, 2024
· 1 comment
Labels
8.1.xBranchBugType: BugCheckoutFOCategory: Front OfficeReadyStatus: Issue is ready to be worked onTrivialSeverity: trivial bug > https://build.prestashop.com/news/severity-classificationVerifiedThe issue has been reproduced
In the purchase funnel, if there is more than one address and the customer chooses the address that is not selected by default, the choice is lost if the customer clicks on the link to enter a different address for the billing process.
Example on a default PrestaShop environment :
The client has two delivery addresses and one is selected by default:
The client chooses the other delivery address (and not the one by default):
The client then clicks on the linK to add another address ('L'adresse de facturation ') for the billing process:
Then the address by default is once again selected and not the one chosen in the previous step.
Expected behavior
The delivery address chosen by the client must be still selected when he wants to enter a different billing address
Steps to reproduce
• Enter two delivery addresses or more
• Put an item in the cart and begin the order process
• Go to the address part of the purchase funnel
• Selected another delivery address than the one selected by default
• Click on the link to enter a different address for the billing process
You’ll see that the delivery address is not the one previously selected.
PrestaShop version(s) where the bug happened
8.1.5
PHP version(s) where the bug happened
all
If your bug is related to a module, specify its name and its version
No response
Your company or customer's name goes here (if applicable).
I reproduce the issue with PrestaShop version 8.1.x, I'll add this to the backlog so it can be fixed.
Please be aware that some issues might take a very long time to be resolved. If this one is important to you and you cannot wait for it to be fixed on the project’s own time, we strongly suggest you consider contacting a professional to help you.
If you fix the issue on your end, please contribute it back to the project. Remember that the more people contribute, the better PrestaShop becomes for everyone.
Thank you
paulnoelcholot
added
Trivial
Severity: trivial bug > https://build.prestashop.com/news/severity-classification
FO
Category: Front Office
Ready
Status: Issue is ready to be worked on
Checkout
Verified
The issue has been reproduced
8.1.x
Branch
and removed
New
New issue not yet processed by QA
labels
May 2, 2024
8.1.xBranchBugType: BugCheckoutFOCategory: Front OfficeReadyStatus: Issue is ready to be worked onTrivialSeverity: trivial bug > https://build.prestashop.com/news/severity-classificationVerifiedThe issue has been reproduced
Prerequisites
Describe the bug and add attachments
In the purchase funnel, if there is more than one address and the customer chooses the address that is not selected by default, the choice is lost if the customer clicks on the link to enter a different address for the billing process.
Example on a default PrestaShop environment :
The client has two delivery addresses and one is selected by default:
The client chooses the other delivery address (and not the one by default):
The client then clicks on the linK to add another address ('L'adresse de facturation ') for the billing process:
Then the address by default is once again selected and not the one chosen in the previous step.
Expected behavior
The delivery address chosen by the client must be still selected when he wants to enter a different billing address
Steps to reproduce
You’ll see that the delivery address is not the one previously selected.
PrestaShop version(s) where the bug happened
8.1.5
PHP version(s) where the bug happened
all
If your bug is related to a module, specify its name and its version
No response
Your company or customer's name goes here (if applicable).
@202ecommerce
The text was updated successfully, but these errors were encountered: