UTF-8 special character issue in widgets

[jsakars]

Steps to reproduce

1. Install Magento 2.0.4
2. Add CMS Page Link or other widget type which accepts input parameters
3. Enter Latvian UTF-8 special characters glāžšķūņu rūķīši in input parameter
4. See video for details

Expected result

1. Widget is added correctly with UTF-8 characters

Actual result

1. Widget is added but UTF-8 special characters are broken
2. Error is show when hiding editor, fixing characters manually and showing editor again

[kristaps-aksjonovs]

Same issue. Maby any ideas about quickfix ?

[kristaps-aksjonovs]

@werdlv One way is to add widget using Insert widget not wysiwyg, error pop will show up, but on frontend content will be ok.

[shiftedreality]

Hi @werdlv

Thank you for reporting. Looks like an issue with TinyMCE. I created internal ticket MAGETWO-52850 to investigate and fix.

[piotrekkaminski]

We are nearly done fixing this issue and should be merged soon.

[jsakars]

@piotrekkaminski FYI - still present in 2.1.0

[pantaoran]

Looks like my report in #5708 duplicates this older issue more or less. I didn't find this one when I searched...

[janepoltoratskaya]

is there any update on this issue?

[DevXeni]

Just now I've got the same error. Bug is not fixed (magento 2.1, installed - July 2016). I think it's TinyMCE configuration. Maybe, need to set "entity_encoding" to "raw" and it will not convert our utf8 characters to a "named entity"...

[enrico69]

Idem. Still present in Magento EE 2.1 (installed in july 2016).

[ziiljuks]

Still present in Magento CE 2.1.1

[tkacheva]

Issue is fixed in mainline (not 2.1.x)
54df23a

[irenelagno]

This issue will be delivered to 2.1.x in the scope of MAGETWO-57051

[mhauri]

Would be great to get this released as soon as possible.

[mhauri]

@piotrekkaminski Still present in 2.1.3, why wasn't this merged from develop into 2.1.3?

[mhauri]

Still present in 2.1.4

[maksek]

The fix scheduled for 2.1.9

[mhauri]

@maksek why so late, 2.1.5 will be a copyright update version only, but why not in 2.1.6?
What's the planned release cycle, based on the latest releases it's around 2 months between each release, so 2.1.9 will be 8 to 10 months away.

[maksek]

@mhauri 2.1.9 will be sooner. We will share our patch release roadmap soon. 2.1.6 will be security update, 2.1.7 will be fixes. But if the issue will have more votes, it may be sooner than 2.1.9. Use upvoting.

[koenner01]

Relates to #7249.
Commit where this has been fixed is referenced there too in case you want to patch this in your project

[pantaoran]

@maksek Is that promised patch release roadmap out yet? I would be very interested to see it.

[veloraven]

Internal ticket for ver. 2.0 - MAGETWO-57816, for ver. 2.1 - MAGETWO-57051
It has been already fixed and will be available in one of nearest releases.

[magento-team]

Internal ticket to track issue progress: MAGETWO-67621