wysiwyg hyperlink issue

[ViktorHavaleshko]

Preconditions and environment

• Magento version - 2.4.*
• Anything else that would help a developer reproduce the bug

Steps to reproduce

1. Go to the admin panel and try to create a CMS page or block:

2. Add some text and click on the "Insert/Edit Link", and add it hyperlink with base url of website using - "{{config path="web/secure/base_url"}}" 3. Save and try to edit hyperlink. We still see "{{config path="web/secure/base_url"}}". 4. Save a block or update the page and we will see the admin URL instead of "{{config path="web/secure/base_url"}}".

if there is a lot of content it is very difficult to replace anything if we have this bug.

Expected result

when editing a block, CMS page or anything that uses the WYSIWYG editor, I want to see the initial link "{{config path="web/secure/base_url"}}test.html" instead of the flow admin URL

Actual result

when saving, refreshing a page or clicking on Show / Hide Editor, instead of {{config path="web/secure/base_url"}} we will get the current admin link

Additional information

No response

Release note

No response

Triage and priority

• 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 @ViktorHavaleshko. Thank you for your report.
To speed up processing of this issue, 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.

[m2-assistant]

Hi @engcom-Bravo. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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.

[m2-assistant]

Hi @engcom-Dash. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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!

---

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

[engcom-Dash]

Hi @ViktorHavaleshko

Thanks for reporting and collaboration.

Verified the issue in magento 2.4 dev instance and the issue is reproducable. Hence, confirming the issue.

when saving, refreshing a page or clicking on Show / Hide Editor, instead of {{config path="web/secure/base_url"}} we are getting the current admin link

Please refer the attached screen recording.

Screen.Recording.2024-03-14.at.12.45.42.PM.mov

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-11600 is successfully created for this GitHub issue.