Unable to insert widget with text value which contains }} string

[ghost]

Preconditions

1. Magento 2.4-develop

Steps to reproduce

1. Go to admin Content -> Pages
2. Click Add New Page
3. Set Page Title to Page Title
4. Expand Content section
5. In the content field, click Insert Widget button
6. Choose any widget which has at least one text input, e.g. Catalog Products List
7. Set widget title: Title}}
8. Click Insert Widget
9. Click Save Page
10. Go in frontend to see the page: <base-url>/page-title

Expected result

1. No errors

Actual result

1. Widget content is incorrectly parsed
   

[magento-engcom-team]

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

[drpayyne]

@magento give me 2.3-develop instance

[magento-engcom-team]

Hi @drpayyne. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @drpayyne, here is your Magento instance.
Admin access: https://i-12087-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[m2-assistant]

Hi @drpayyne. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

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

• 2. 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!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[m2-assistant]

Hi @Parakoopa. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

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

• 2. 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!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[theCapypara]

I tried solving this issue by extending the regex in Magento\Framework\Filter\Template, however after some tests and thinking about it, I don't think this is actually solvable using regex. So to solve this, the directive parsing logic would propably need to be changed.

[m2-assistant]

Hi @engcom-Delta. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

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

• 2. 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!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[magento-engcom-team]

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

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

[m2-assistant]

Hi @engcom-Kilo. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
• 2. 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!
• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[magento-engcom-team]

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

• 7f0f260d3110a055ca1f8fa4886e766dd303b6c1
• 2a48abee8a17331fdea9d3ba4738e5394d73a13b
• e0eb4b0e3000b027b0197cf5603cc5fb8f6b8198
• cb0b3d407dc1ac5c42e202a515a2aee97574b57d
• 1f84319d6905dc9cc862fd0cb1244489b44f5052
• f55eeb49d1e83b268f0c45bdce73eb2d0689b88f
• ae3d3df4752dfcac5256ddb5014ce02b19e8a529
• a2346f4697a76f1d9905dc9968a79b57a9909e2b
• 74325ef39fd1c1e4e957747dc2d29ca3e73f4cf8
• 0ac2e5d691f5bccbdb2fba896bb1c22ff6a0fa80
• edd340130b92015e3ecd6e03e93ca75111610afe
• ace8a6fd54d920b01533668f7f0b2942ec4b3def
• 01b7906cd3e339c0467f6cc9af6d681c7627482b

The fix will be available with the upcoming 2.4.2 release.