Open ghost opened 6 years ago
Actually if you modify your WYSIWYG, change the editor to HTML tab and update it's looks work fine
I don't seen an 'HTML' tab, but there is a 'Visual' and a 'Text' tab on the WYSIWYG editor for that field. 'Visual' was selected. I switched to 'Text' and the content I entered was saved. If I switch back to 'Visual' though, I still can't seem to save anything I enter. Thanks though, this at least lets me add content.
I believe this issue was fixed in one of the latest releases. @mr-king can you confirm?
Hi there, I have the same issue, do you have someone on it ?
@ledjay can you let us know what WP version you're using? I also assume you're using the normal Block Editor, correct? Are you using the Gutenberg plugin?
I cannot reproduce this issue in the block editor.
Happens to me too. Using WP 5.6.2, CPT with Pods, Rest API is enabled and TinyMCE is added as additional field. The TinyMCE is empty and uneditable on load. You can get around it by changing the TinyMCE to HTML mode and reloading the page. It will then load fine and you can then switch to the visual editing mode and edit away.
But if I load the page while the TinyMCE is still in visual editing mode, the visual editor content is empty and uneditable. It is only the visual editor mode of TinyMCE though. If I switch to HTML mode I can see the content as HTML, but switching back to visual editor mode still shows the empty uneditable editor.
Issue Overview
After enabling the REST API on a Custom Post Type Pod, WYSIWYG fields no longer update properly.
Expected Behavior
After selecting the 'Enable' checkbox on the REST API tab for my Pod and saving, I should still be able to update existing WYSIWYG fields in my pods.
Current Behavior
After enabling the REST API for a Pod, updates to WYSIWYG fields are no longer saved to the database. Other types of fields seem to be unaffected. If I change the WYSIWYG field to a "Plain Paragraph Text" field, it can then be updated. If I change it back to a WYSIWYG field, it can no longer be updated. If I leave it as a WYSIWYG field and uncheck the 'Enable' checkbox on the REST API tab for my Pod, it can then be updated.
By 'updated', I mean my changes are saved to the database. Also, I see no errors in my web server's logs or in the javascript console of my browser.
Steps to Reproduce (for bugs)
Possible Solution
WordPress Environment
Pods Package Export (helpful!)
Workaround or Alternate Solution Until Bug is Addressed
I'm not using Gutenberg in production, so I'm not worried about a workaround.
Related Issues and/or PRs