Sending emails from Admin in Multi-Store Environment defaults to Primary Store

[lee586]

Preconditions

1. Tried on versions 2.18-2.2
2. Cent OS 7, PHP 7.1.10

Steps to reproduce

1. Create two stores: ABC.com (primary) and XYZ.com
2. Have customer place order on XYZ.com
3. Go into admin, click on order from XYZ.com, and resend order confirmation email

Expected result

1. Should send email using FROM EMAIL and FROM NAME of store XYZ.com

Actual result

1. Magneto sends correct email content, but FROM EMAIL and FROM NAME are both from the primary store ABC.com instead of the store the customer used, XYZ.com. Creates confusion for customer as the FROM information is not the store from which they placed the order. Happens on any email resent from admin--confirmation, shipping, credit, etc.

[magento-engcom-team]

Hello @lee586. Tanks for reporting. Please clarify You mean two stores on the same website or two stores on two different websites.

[lee586]

Sorry for not clarifying. Two different websites.

[magento-engcom-team]

@lee586, thank you for your report.
We've created internal ticket(s) MAGETWO-82906 to track progress on the issue.

[EugenOrosan]

Any fixes for this ? This is a big issue because customers receive emails from the default sender instead of order website sender.

[ArroganceEmu]

The problem is the same if both shops are under the same website.

[okorshenko]

The issue has been fixed and delivered to 2.2-develop branch. Will be available with upcoming patch release

[okorshenko]

Hi @lee586. Thank you for your report.
The issue has been fixed in magento-engcom/magento2ce#1325 by @magento-engcom-team in 2.3-develop branch
Related commit(s):

• e84cb3e
• 742819b
• cc2b11f
• ae8b187
• 35b3c02
• eae8936
• 90e4923
• b098dbc
• e8e4cdd
• 058e5e5
• 9368d5d
• bf19409
• a15ec34
• 9e4ce76
• 0995681
• 6772a2d
• b0d6bfc
• b037357
• 8de5951

The fix will be available with the upcoming 2.3.0 release.

[Hajo-Magre]

Hi, the link above is private or broken and gives a 404. The list of related commits is large and does seem to adress a lot of other issues, that I am not experiencing. Of course they could be heavily related.

I am on 2.2.3 right now. The fix for this is in 2.3.0. Is there a rough ETA for it's arrival? How many minor versions will we have in between?

In others words: my customers are receiving 'wrong' email, that is: not from the shop they ordered from. This is a serious issue at this time.

Has anyone figured out a temporarily fix or workaround for this issue?

(Besides: this issue received the label "fixed in 2.2.x" but I can confirm that is NOT the case in 2.2.3.)

== UPDATE:
found a temporarily fix, I think:

1. Magento has 5 emailadresses to configure in General > Stores Emailadresses. I've set one of them to an emailadress of my second store, but I set that value at top level i.e. "default config", NOT at the store view or website level. I chose to use "Custom Email 2" for this purpose.
2. Went to Sales > Sales emails and configured each email instance to use "Custom Email 2" as email sender, but only in the scope of my second store or website.
   Result: Magento can read the emailadress and from name from a top level (default config) instead of the store view, where it al goes wrong.
   I think this fixed it for now. Will report back here if anything else pops up.

[zack6849]

Is there not going to be a backport to 2.1 for this fix?

[ritschi72]

Still got that problem in 2.2.4 ...

[diedburn]

This broke the normal confirmation email #14952

[juandosil]

Same issue here with Magento 2.2.4 with only one store

[cleardarren]

same issue with 2.2.5 multistore

[gwharton]

Note. If you dont use the amazom payments module, disable or uninstall it to get this working again. This update triggered a bug in that module.

[juandosil]

Just disable it bin/magento module:disable Amazon_Core Amazon_Login Amazon_Payment and it´s working fine again.
Thank so much

[magento-engcom-team]

Hi @lee586. Thank you for your report.
The issue has been fixed in #18471 by @gwharton in 2.3-develop branch
Related commit(s):

• ad50297e7bf4ea39db62f0969579a1ca8eb5f1a3
• e16ff74e4f5f24a4a2530b6aced6ef50032515e0
• 621d2cfeaf8e0a15e592cdc001c856385b3cbd83
• b6f9e48289119117df230b6578ac9ff3d69e4996
• 0dc85785e522e2be8c72dfeaee7e9f5054195034
• 122019c953037df74ef97245a42b274eae2e6639
• 193c6c2f6facf7276c1c8858d29ea3b847062ef5
• bd0aa57cc837918335015d051f08cf380dc186d0
• 523b0464966f81f1f01aa13073092bfddf363219
• 424929fe9aee1005601cc2c9c7ad0090741be723
• c32ca7a0d58cbc57276349b26eb5ecd38451fd2d
• e39ce7a3f2a7e6ee134cff9a097b7321756c32cf
• 99621b32f8c7d3d12f83db7e67f5f1c1ef3e7f31
• f171c9d6ab035439ffb6374ec14dd8d51123dcd2

The fix will be available with the upcoming 2.3.1 release.

[magento-engcom-team]

Hi @lee586. Thank you for your report.
The issue has been fixed in #18472 by @gwharton in 2.2-develop branch
Related commit(s):

• 82a635b3a4eb0fd0e2f030d82495ab717ee11db5
• 16afc0962463261e4464456b9bdaad4e8f3be924
• 47c5f72c9196dc77b50db3c36ec99719a69a18a0
• 8d7a4513ddf4b759a6c6a0d2ace04aa714a396df
• a7cd527a6896c3a2f204e2771b92496ef4089f4e
• 491d7f133591c64346cb54c2392d0ef212333b1a
• 490e5d22074224ec1965a391abfffc379c31d0ee
• b19b3ed195b870f16a00c673e435b5b9b8184227
• 9f34fd631a55ded6d8a458d219edfc23c1bc5f9b
• 66478ec59d6cbf77d538f2ea112f32997e491bf8
• cc34f00113e1e644e92002f82d34c4bf36aa0e26
• fb572d887f0ce156c8f3ac149de7b8f06835623d
• 59a4e57a0c36671ff84e8398f413253610a512ac
• a8bcb8bb8442a649bf1e62400ca6f147023e53c6
• 573cf7a9fee7c2d8ca9c1c25fe909c93ccf06c49
• ef635bf6b8ecf67c729deb38df05c81b9e5b5359
• daa8996bbda2e7ca938a7e3a3e8afc40502cd98f

The fix will be available with the upcoming 2.2.9 release.

[Rickertje]

@magento-engcom-team Are you sure this has found its way into 231 ?

[okorshenko]

Hi @Rickertje
Could you please clarify your question? Are you still able to reproduce the issue on latest 2.3-develop?

[Rickertje]

I'm responding to this comment

I was expecting to see this fixed in 231 but Im still experiecing the orginal problem in 231.
Have not checked 23develop since I'm not a developer

[okorshenko]

Sure, we will double check this issue.

[m2-assistant]

Hi @stoleksiy. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[soleksii]

Hi @Rickertje ! Thank you for your collaboration!

I'm not able to reproduce the issue on latest 2.3-develop and 2.3.1 release.

Steps to reproduce:

1. Create two websites: magento23.loc (primary) and magento23second.loc
2. Have customer place order on magento23second.loc
3. Go into admin, click on order from magento23second.loc, and resend order confirmation email

Actual Result:
Magneto sends correct email content, FROM EMAIL and FROM NAME are both from the second store
magento23second.loc

Could you please provide more details how to reproduce the issue?

Thanks!

[Rickertje]

Hi @stoleksiy . I can reproduce this but only on my own 231 install which was upgraded from 227 recently. So its not a fresh install. Could be that some custome code is interfering. I dont know and I'm not in the position to thorougly investigate this right now. For now you can close the issue again. Thank you very much for taking the time to check this for me. Regards. Rick

[okorshenko]

Closing the issue based on comment above

[angelflo]

still got the pb with magento 2.2.10 ? can someone explain me clearly what to do to fix this ?