# \[FIX AVAILABLE\] Confirmation buttons broken in Russian/Arabic/Chinese - PR #15805 submitted

**URL:** <https://forum.mautic.org/t/fix-available-confirmation-buttons-broken-in-russian-arabic-chinese-pr-15805-submitted/37211>\
**Category:** Product Support\
**Tags:** development\
**Created:** [January 23, 2026, 8:32pm UTC](https://forum.mautic.org/t/fix-available-confirmation-buttons-broken-in-russian-arabic-chinese-pr-15805-submitted/37211 "2026-01-23T20:32:17Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![zaharovrd](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/zaharovrd/32/7799_2.png) [@zaharovrd](https://forum.mautic.org/u/zaharovrd)\
**Post date:** [January 23, 2026, 8:32pm UTC](https://forum.mautic.org/t/fix-available-confirmation-buttons-broken-in-russian-arabic-chinese-pr-15805-submitted/37211/1 "2026-01-23T20:32:17Z")

</div>

## Issue: Confirmation Buttons Show Unicode Escapes in Non-Latin Languages

**Status:** ✅ Fix submitted as PR #(ваш номер PR)  
**Affects:** Mautic 6.x & 7.x  
**Priority:** High (internationalization bug)

### The Problem

Users of Russian, Ukrainian, Arabic, Chinese, Japanese, and other non-Latin languages see garbled text in confirmation buttons throughout Mautic:

**Example:** “Отмена” (Cancel) appears as `\\u041E\\u0442\\u043C\\u0435\\u043D\\u0430\`

### The Solution is Ready!

I’ve already submitted a Pull Request with the fix:  
**PR** #15805: [Fix Unicode character encoding in confirmation modal buttons](https://github.com/mautic/mautic/pull/15805)

The fix is simple and safe:

```auto
diff

{%- set attr = attr|merge({‘data-cancel-text’: cancelText|escape(‘js’)}) %}

{%- set attr = attr|merge({‘data-cancel-text’: cancelText|escape(‘html_attr’)}) %}

```

### Why This Matters

1. **Affects all non-English installations** - this isn’t a niche issue
2. **User-facing bug** - looks unprofessional to end users
3. **Simple, low-risk fix** - just changes escaping context
4. **Already tested** - works in both 6.x and 7.x

### Call to Action for Community

If you use Mautic with non-Latin languages, please:

1. **Confirm this issue** affects you (comment below)
2. **Review the PR** if you’re a developer
3. **Upvote** this topic for visibility
4. **Tag maintainers** who should see this

### Call to Action for Core Team

@mautic/team @developers

This PR is ready for review:

✅ Minimal change (one line)  
✅ Properly tested  
✅ Affects both 6.x and 7.x  
✅ Community impact confirmed

Can we prioritize this for the next patch releases?

### Current Status

- **PR:** Submitted and waiting review
- **Testing:** Verified working in 6.x & 7.x
- **Risk:** Low (security-maintaining escaping change)

### Screenshots

 ![Before_fix](https://us1.discourse-cdn.com/flex020/uploads/mautic/original/2X/e/ed6e9fed04473e41c5e2714d42fc9ad0a19bee52.jpeg)

**Before:** `\u041E\u0442\u043C\u0435\u043D\u0430`

 ![After_fix](https://us1.discourse-cdn.com/flex020/uploads/mautic/original/2X/3/386aae435b0d27ac4192873f843a68b48d6b2eeb.jpeg)

**After:** `Отмена`

* * *

---

<div class="post-metadata">

**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\
**Post date:** [January 25, 2026, 9:11pm UTC](https://forum.mautic.org/t/fix-available-confirmation-buttons-broken-in-russian-arabic-chinese-pr-15805-submitted/37211/2 "2026-01-25T21:11:35Z")

</div>

Thanks for this! Instructions for testing can be found at [Tester — Mautic Community Handbook 0.1 documentation](https://mau.tc/tester). I added a note on your PR as it needs rebasing, but hopefully the branches won’t have diverged too much at this point in time.

---

<div class="post-metadata">

**Author:** ![zaharovrd](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/zaharovrd/32/7799_2.png) [@zaharovrd](https://forum.mautic.org/u/zaharovrd)\
**Post date:** [January 26, 2026, 7:30pm UTC](https://forum.mautic.org/t/fix-available-confirmation-buttons-broken-in-russian-arabic-chinese-pr-15805-submitted/37211/3 "2026-01-26T19:30:12Z")

</div>

I rebased it - is everything ok?  
You also need to upload branch 6. in 6.0.8 for example

---

<div class="post-metadata">

**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\
**Post date:** [January 26, 2026, 8:26pm UTC](https://forum.mautic.org/t/fix-available-confirmation-buttons-broken-in-russian-arabic-chinese-pr-15805-submitted/37211/4 "2026-01-26T20:26:30Z")

</div>

It won’t be fixed in 6, as that version is in security-only support now:

> **[Mautic Releases - Mautic](https://mautic.org/releases/)**
>
> Mautic follows semantic versioning for its releases:

So we’d fix this in the 7.0.1 release ideally.

---

<div class="post-metadata">

**Author:** ![zaharovrd](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/zaharovrd/32/7799_2.png) [@zaharovrd](https://forum.mautic.org/u/zaharovrd)\
**Post date:** [January 26, 2026, 8:32pm UTC](https://forum.mautic.org/t/fix-available-confirmation-buttons-broken-in-russian-arabic-chinese-pr-15805-submitted/37211/5 "2026-01-26T20:32:09Z")

</div>

It’s a pity and strange, because, It’s too early to use version 7 for production.  
Is Mautic 6 an intermediate version?

---

<div class="post-metadata">

**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\
**Post date:** [January 26, 2026, 8:42pm UTC](https://forum.mautic.org/t/fix-available-confirmation-buttons-broken-in-russian-arabic-chinese-pr-15805-submitted/37211/6 "2026-01-26T20:42:49Z")

</div>

6.0 is LTS, and so is 5.2. Those are both in long term support, with security fixes only.

7.x will have active development with bug fixes, security fixes and features for the next 12 months, and then will have security fixes only until the end of Q4 2027 when it’ll come to the end of security support.

While 7 is our new major release, most folks are waiting on 5.2 until the end of security support (end of Q2 2026) and then transitioning over to 7 directly, and skipping 6. Failing that you can get Extended Long Term Support for 5 to give you an extra two years of using 5, or one year for using 6, if you can’t update yet.

Read about the reason for our shorter release cycle on 6 and generally how we manage support periods here: [Introducing Mautic's new release strategy: Long Term Support for enhanced stability and continuity - Mautic](https://mautic.org/blog/introducing-mautics-new-release-strategy-long-term-support-elts/).
