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

Admin fields that use WYSIWYG don't pass the js validation #933

Closed
tzyganu opened this issue Jan 8, 2015 · 4 comments
Closed

Admin fields that use WYSIWYG don't pass the js validation #933

tzyganu opened this issue Jan 8, 2015 · 4 comments
Labels
bug report Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Progress: needs update

Comments

@tzyganu
Copy link
Contributor

tzyganu commented Jan 8, 2015

In the admin add forms, the fields that use the WYSIWYG do not pass the javascript validation until you click show/hide editor.

Preconditions:

  • Magento2 0.42.0-beta2
  • CMS Editor enabled by default

Steps to reproduce:

  • Go to CMS->Pages->Add page
  • Fill in all required fields (including the content field)
  • Save Page

Expected result:

  • The paged is saved

Actual result:

  • There is js validation error message below the button Show/Hide editor - Bu the way, I think the error message should go under the editor not under the button.
  • Clicking on "Show/hide editor" once or twice allows me to save the form.
@maksek maksek added the MX label Jan 8, 2015
@kokoc kokoc added PS and removed MX labels Jan 30, 2015
@mazhalai
Copy link
Contributor

@tzyganu thank you for reporting this issue. We have created MAGETWO-33484 to track it internally.

@sshrewz sshrewz added bug report Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development labels Jan 30, 2015
@tzyganu
Copy link
Contributor Author

tzyganu commented Mar 19, 2015

I might add that on the beta11 the editor is not working at all. At least in the CMS->pages section.

@vpelipenko
Copy link
Contributor

@tzyganu, issue is fixed. Please, look at the fix and provide your feedback.

@tzyganu
Copy link
Contributor Author

tzyganu commented Aug 11, 2015

@vpelipenko I confirm that this is fixed. Thank you.

@tzyganu tzyganu closed this as completed Aug 11, 2015
magento-engcom-team added a commit that referenced this issue Sep 25, 2019
 - Merge Pull Request magento/graphql-ce#933 from akamuraasai/graphql-ce:deprecate-customer-group-id
 - Merged commits:
   1. 01e5ab5
   2. dbbcdb1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Progress: needs update
Projects
None yet
Development

No branches or pull requests

6 participants