Skip to content

Error in TinyMCE when typing %-character #8369

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Arriba99 opened this issue Feb 1, 2017 · 4 comments
Closed

Error in TinyMCE when typing %-character #8369

Arriba99 opened this issue Feb 1, 2017 · 4 comments
Labels
bug report Component: Catalog Fixed in 2.2.x The issue has been fixed in 2.2 release line Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release

Comments

@Arriba99
Copy link

Arriba99 commented Feb 1, 2017

Preconditions

  1. Magento 2.1.3 CE
  2. PHP 5.6.21

Steps to reproduce

  1. Open product or page
  2. Type %-character in TinyMCE Editor field

Expected result

  1. Everything should be fine

Actual result

  1. Immediatly an error is displayed (2 times):
    error: error in [unknown object].fireEvent(): event name: tinymceChange error message: malformed URI sequence

unbenannt-1

Once the %-character is typed in the editor, the error pops up again everytime you type in the editor field. All other characters doesn't trigger the error. When the product or page is saved, the %-character gets deleted in the text.

We use another magento installation for testing and there the error doesn't show up.

Kind regards!

@fxdegroot
Copy link

We got the exact same problem on Magento 2.1.4 EE

@hostep
Copy link
Contributor

hostep commented May 14, 2017

That's really strange, since the code which causes this problem is only active in the develop branch and not in a previously released version. See #9452 for more details.
Although the error message is slightly different (malformed URI sequence vs URI malformed), so maybe this is then a different issue?

@veloraven
Copy link
Contributor

We already have internal ticket for ver. 2.1 - MAGETWO-68810

@veloraven veloraven added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Jun 21, 2017
@magento-engcom-team magento-engcom-team added 2.1.x Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development bug report Component: Catalog Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed and removed G1 Passed labels Sep 5, 2017
@magento-engcom-team
Copy link
Contributor

@Arriba99, thank you for your report.
The issue is already fixed in 2.2.0

@magento-engcom-team magento-engcom-team added Fixed in 2.2.x The issue has been fixed in 2.2 release line Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release labels Sep 20, 2017
magento-devops-reposync-svc pushed a commit that referenced this issue Aug 29, 2023
[Performance] REST API Import JSON
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Component: Catalog Fixed in 2.2.x The issue has been fixed in 2.2 release line Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release
Projects
None yet
Development

No branches or pull requests

5 participants