Closed BrookeDot closed 3 months ago
@BrookeDot Disabling TinyMCE is an experimental feature provided by the Gutenberg plugin and the usage should be avoided in production. I don't think this can be classified as a bug in RSA. @dkotter any thoughts on this?
I think that's correct. Something we can keep an eye on to see if this ever gets merged into WordPress core and fix then but otherwise if anyone runs into this problem, we can suggest they disable that setting in Gutenberg
Closing this for now as not fixing.
Describe the bug
I've been experiencing a bug that was driving me mad and finally was able to replicate it. I was unable to set the "message" field in the plugin's settings. Instead I just saw an empty field.
I was able to set a message with CLI;
When I started disabling plugin's I disabled Gutenberg and the filed returned:
Looking through the Gutenberg settings I found the "Disable TinyMCE and Classic block" setting. When this setting is enabled the message field does not appear.
Looking at the 's files I found the following: https://github.com/WordPress/gutenberg/blob/ae7df52f58baf6289c58b5da76a884ff400cfa3f/lib/experimental/disable-tinymce.php#L10-L20
I'm assuming the solution here is to ensure the "Reading" page is set to require the classic editor (or to upgrade the message field to use the Block Editor)
Steps to Reproduce
Screenshots, screen recording, code snippet
No response
Environment information
Tested on Windows, MacOS (several versions). Firefox, Brave, Edge, etc.
WordPress information
WordPress Version | 6.4 WordPress Multisite | No WordPress Memory Limit | 512M WordPress Debug Mode | No WordPress Debug Log | No WordPress Script Debug Mode | No WordPress Cron | Yes WordPress Alternate Cron | No Background tasks | Yes
NGINX
PHP 8.2.11
Code of Conduct