Static CMS image urls when using a different (sub)domain for custom admin url

[elouwerse]

Preconditions (*)

1. Magento 2.4.2

Steps to reproduce (*)

1. Admin panel » Stores » Configuration » General » Content Management » Use Static URLs for Media Content in WYSIWYG: No
2. Admin panel » Stores » Configuration » Advanced » Admin » Admin Base URL » Use Custom Admin URL: Yes
3. Set admin to a different (sub)domain than the actual store url.
4. Add/edit a CMS page, static block or product page
5. Add image

Expected result (*)

1. Media tag with relative image url
2. <img src="{{media url="wysiwyg/test-image.png"}}" alt="">

Actual result (*)

1. Media tag with static Magento admin url instead of store url
2. <img src="{{media url="https://dev.magentotest.local/wysiwyg/test-image.png"}}" alt="">

This issue is caused by inconsistend use of $this->_storeManager->getStore() in /vendor/magento/module-cms/Helper/Wysiwyg/Images.php
Line 214: $this->_storeManager->getStore()
Line 299: $this->_storeManager->getStore($this->_storeId)

---

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 @elouwerse. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

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

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

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

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, please 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

[magento-engcom-team]

@Den4ik Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

[magento-engcom-team]

✅ Confirmed by @Den4ik
Thank you for verifying the issue. Based on the provided information internal tickets MC-42160 were created

Issue Available: @Den4ik, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[sidolov]

Hi @elouwerse. Thank you for your report.
The issue has been fixed in #33095 by @engcom-Kilo in 2.4-develop branch
Related commit(s):

• a61277cb287388f050ee93d1d2baa1cc95d3b22c

The fix will be available with the upcoming release.