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

CFS WYSIWYG field displays differently in Gutenberg #3302

Closed
chthonic-ds opened this issue Nov 2, 2017 · 7 comments
Closed

CFS WYSIWYG field displays differently in Gutenberg #3302

chthonic-ds opened this issue Nov 2, 2017 · 7 comments
Assignees

Comments

@chthonic-ds
Copy link

@chthonic-ds chthonic-ds commented Nov 2, 2017

Issue Overview

CFS (Custom Field Suite) WYSIWYG field displays differently in Gutenberg vs. Classic Editor.

Steps to Reproduce (for bugs)

  1. Install and activate Custom Field Suite plugin: https://wordpress.org/plugins/custom-field-suite/.
  2. Create a WYSIWYG field and enable for posts/pages.

Expected Behaviour

The WYSIWYG field will render with equivalent functionality in Classic Editor and Gutenberg.

Current Behaviour

The WYSIWYG field renders with TinyMCE buttons in Classic Editor and without TinyMCE buttons in Gutenberg.

Gutenberg 1.6.0
Windows 10
Chrome 61.0.3163.100 (Official Build) (64-bit)

Classic Editor

cfs-wysiwyg-view-classic-editor

Gutenberg

cfs-wysiwyg-view-gutenberg

@BE-Webdesign

This comment has been minimized.

Copy link
Contributor

@BE-Webdesign BE-Webdesign commented Nov 2, 2017

Hi @chthonic-ds,

Thank you for the report. Most likely TinyMCE is not being enqueued properly or something of that nature. I will look into it. Is CFS on the WordPress.org Plugins Repository?

@chthonic-ds

This comment has been minimized.

Copy link
Author

@chthonic-ds chthonic-ds commented Nov 2, 2017

Thanks @BE-Webdesign. The repository link is noted in the issue: https://wordpress.org/plugins/custom-field-suite/.

@dev4press

This comment has been minimized.

Copy link

@dev4press dev4press commented Nov 16, 2017

This is not the issue with this plugin only. Any plugin that uses wp_editor() to embed TinyMCE editor in metaboxes is broken, sometimes completely, in some cases, only TinyMCE Visual tab is broken and Text tab shows toolbar, but no content area.

@adampatterson

This comment has been minimized.

Copy link

@adampatterson adampatterson commented Nov 17, 2017

This is the same for ACF WYSIWYG fields. It also prevents the Add media, insert images, and add forms from working in using Gravity Forms, and Unsplash Image plugin.

Unfortunately because of this issue. This plugin is unusable for me.

@sc0ttkclark

This comment has been minimized.

Copy link

@sc0ttkclark sc0ttkclark commented Nov 29, 2017

Yep Pods is broken too. See below for an example, I had to click into Text tab since Visual tab is empty to type that text shown.

screen shot 2017-11-29 at 4 01 29 pm

@nderambure

This comment has been minimized.

Copy link

@nderambure nderambure commented Feb 7, 2018

Yep, it's for any metabox with a wp_editor() function call as said by @dev4press.
Too time consuming for me to look into the code, I don't know the tinymce part of WP, either Gutenberg at all, but it's a major issue, no doubt about that.

@BE-Webdesign BE-Webdesign self-assigned this Feb 8, 2018
@BE-Webdesign

This comment has been minimized.

Copy link
Contributor

@BE-Webdesign BE-Webdesign commented Feb 8, 2018

I will do my best to resolve this somehow, hopefully before the end of the month.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can’t perform that action at this time.