Save which language was used during checkout ("checkout_langcode")

reroll patch to make possible to apply on 2.36

I just ran into something related and I'm not sure, if it should be solved combined here or as separate issue. I'm NOT using the patch from this issue (yet):

If you create an order in one language, proceed with the first checkout step (confirm so that the order status changes from cart to something else) and then go back to a regular page with cart, the cart is empty, if you're changing to a different language. Going back into the checkout with that different language, also shows the checkout empty.

Returning to the original language, the cart content and the checkout shows again. Of course, it would be expected ot see the contents in both languages, just like before the checkout started.

Is this closely related to this issue or should I better create a separate one?
Can you reproduce it?

Is this closely related to this issue

I don't think. This issue is about adding the langcode on the order once it's completed. To be able to know in which language the order has been completed.

Can you reproduce it?

Tried on one of my commerce project and I don't reproduce your issue. I wonder if you do't have some custom code / contrib module which implements permissions based on the language for product / order item.

@flocondetoile thanks for your feedback! I'll try to reproduce that in a vanilla Drupal Commerce installation. No modules for that, but of course might be a side effect of another module. I'll try and if I'm able to reproduce it, create a separate issue, thanks!

Path stores checkout language but how can send checkout receipt or resend receipt in checkout language?

Now i receive mail with user preferred language for some text and user interface language for other text.

May be usefull to resend mail in checkout language form admin.
Thank you

I guess this still makes sense. At least when finishing the order, the language should be stored into the order entity, so if the user is anonymous or not, we're able to determine in which language the order was made and base all further emails on that.

At least for customers with a user account, I don't see many further use-cases. Eventually, if you provide further after-sales things like parcel tracking or sth. like that based on the order, it will also be useful.

All in all it totally makes sense logically to have that information in the order.

I guess this should go into 3.0.x then? Do we need anything else here, besides preparing a fresh MR?

Should the use of this for the order confirmation email be done here or in a follow-up? A related issue at commerce_email should be created, once this is ready.

Any other final comments @jsacksick? Guess it makes sense to move this over the finish line for the reasons given above...

There's also the older discussion at 📌 Clarify order language behavior Needs work which might have important information.