The default luma logo is shown on frontend order print page

[ihor-sviziev]

During migration from Magento 2.3.x to 2.4.3-p1 we noticed an issue - the print order/invoice/credit memo pages (on frontend) started showing a default luma logo instead of the logo that is shown on the entire website.

Preconditions (*)

1. Magento 2.4.3
2. Luma theme
3. Set custom logo in the header on the frontend

Steps to reproduce (*)

1. Go to the frontend
2. Place some order
3. On the frontend go to My Account > My Orders > View Order > Print Order

Expected result (*)

1. If you explicitly defined a custom logo for emails - that logo should be shown (the highest priority) - Config path sales/identity/logo_html
2. If you specified a custom frontend logo - that logo should be shown (medium priority) - Config path design/header/logo_src
3. If you didn't specify both custom logo for emails and frontend logo - the default luma should be shown (the lowest priority)
   The same flow should be for invoices and credit memos.

Actual result (*)

1. If you explicitly defined a custom logo for emails - that logo should be shown (the highest priority) - ✔ works fine
2. If you specified a custom frontend logo - that logo should be shown (medium priority) - ❌ doesn't work, but worked on Magento 2.3.7-p2.
3. If you explicitly defined a custom logo for emails - that logo should be shown (✔ works fine)

Additional info

The issue appeared after the following commit: 4531c76
It had to fix the case when the first option didn't work fine.

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @ihor-sviziev. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-Hotel. 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.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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. Add label Issue: Confirmed once verification is complete.

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

[engcom-Hotel]

Hello @ihor-sviziev,

Thanks for posting the issue!

We have tried to reproduce the issue by upgrading Magento from 2.3.7 to 2.4.3-p1 and the issue is reproducible for us. We have followed the exact same steps mentioned in the main description. Please have a look at below screenshots for reference:

• Before Upgrade:
  Admin Dashboard
  

Order Frontend

• After Upgrade
  Admin Dashboard
  

Order Frontend

Hence confirming the issue.

Thanks