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

Front office connection from back office order #33906

Closed
2 tasks done
Belyce32 opened this issue Sep 11, 2023 · 3 comments
Closed
2 tasks done

Front office connection from back office order #33906

Belyce32 opened this issue Sep 11, 2023 · 3 comments
Labels
Bug Type: Bug Duplicate Resolution: issue closed because already reported Invalid Resolution: issue closed because invalid

Comments

@Belyce32
Copy link

Prerequisites

Describe the bug and add attachments

Since versions 1.7.7, when you create a back office order and you want to finalise the order in the front office, the customer you are supposed to be connected to for this back office order is not connected to the shop.

Expected behavior

once the option to Proceed to payment on the front office has been selected, the customer account must be automatically connected.
This is the behaviour of previous versions. Worked perfectly on version 1.7.5

Steps to reproduce

1.Go to order and create a back office order.
2.Choose an existing customer.
3.Fill in the order and to finalise, select the option PROCEED TO PAYMENT FROM THE FRONT OFFICE.
image

4.The shop opens, but on a customer login page.
image

The customer is not automatically authenticated. You need to go to login and enter your password.
It is impossible to finalise a BO order with a customer account that logs in automatically.

PrestaShop version(s) where the bug happened

1.7.7.4 and 1.7.8.10

PHP version(s) where the bug happened

7.3.33 and 7.2.34

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

No response

@Belyce32 Belyce32 added Bug Type: Bug New New issue not yet processed by QA labels Sep 11, 2023
@Hlavtox
Copy link
Contributor

Hlavtox commented Sep 11, 2023

Duplicate of #30074 and #20977

@Belyce32
Copy link
Author

Belyce32 commented Sep 11, 2023

I applied the fix from #31489
all is ok, thank you

@sallemiines
Copy link
Contributor

Duplicate of #20977

@sallemiines sallemiines marked this as a duplicate of #20977 Sep 11, 2023
@sallemiines sallemiines added Duplicate Resolution: issue closed because already reported Invalid Resolution: issue closed because invalid and removed New New issue not yet processed by QA labels Sep 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Type: Bug Duplicate Resolution: issue closed because already reported Invalid Resolution: issue closed because invalid
Projects
None yet
Development

No branches or pull requests

3 participants