Skip to content
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

Backport of MAGETWO-57675 for Magento 2.1: WYSIWYG editor does not show. #6222 #4828 #6815 #9499

Merged
merged 1 commit into from
May 8, 2017

Conversation

hostep
Copy link
Contributor

@hostep hostep commented May 3, 2017

Description

This is a backport of issue MAGETWO-57675 for Magento 2.1

Fixed Issues (if relevant)

  1. Show/hide Editor not working sometimes #4828: Show/hide Editor not working sometimes
  2. [2.1.0] Sometimes WYSIWYG editor does not show. #6222: [2.1.0] Sometimes WYSIWYG editor does not show.
  3. wysiwyg Editor problem #6815: wysiwyg Editor problem

Reference to commit on the develop branch: 3524943

@ishakhsuvarov ishakhsuvarov self-assigned this May 4, 2017
@ishakhsuvarov ishakhsuvarov added this to the May 2017 milestone May 4, 2017
@magento-team magento-team merged commit 6b07d07 into magento:2.1-develop May 8, 2017
magento-team pushed a commit that referenced this pull request May 8, 2017
[EngCom] Public Pull Requests - 2.1

 - MAGETWO-68903: Backport of MAGETWO-57675 for Magento 2.1: WYSIWYG editor does not show. #6222 #4828 #6815 #9499
 - MAGETWO-68902: Backport of MAGETWO-54798 For Magento 2.1: One page checkout - Street Address should highlight red when data is missing #9500
@magento-team
Copy link
Contributor

@hostep thank you for your contribution. Your Pull Request has been successfully merged

@LucasEasy
Copy link

I went to stores->configuration->content management and by Enable WYSIWYG Editor a chose the option Disable by default and the WYSIWYG editor is working. I can add widges and pictures.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants