The ‘visual’ part of the WYSIWYG pods field doesn’t show anything. The ‘Text’ part does.
This is a brand new install of wordpress 6.5 on a local server today (xammp), no other plugins are installed other than Pods. The only thing I’ve done is added a pods WYSIWYG field to the standard Page type, and enabled Rest-API for that field. When attempting to write in the field when editing the default ‘Sample Page’ which comes with a WordPress install, nothing happens, no text appears. Switching to the Text tab, and I can add text. What could be wrong? Many thanks in advance!
So, I’ve found out several things… Installing the classic editor plugin, solves the problem, because it apparently disables Gutenberg, however, I wish to use Gutenberg. I also found that installing ACF custom fields plugin ( I didn’t do anything with it whatsoever, just installed and activated, nothing else) solves the problem. So something about ACF installation is changing a setting somewhere that resolves the problem.
Any idea what the problem could be? I see this question pop up occasionally, I’ve searched extensively for it, but none of the answers given fitted to my situation. It seems a bit odd, to have to have the ACF plugin installed to fix this
Apart from this one problem, I’m really impressed with pods.
Well that’s actually good news! That gives us some helpful info to maybe limit the scope of where we should be looking by comparing implementations with ACF there.
Sounds like the scripts for the TinyMCE editor are not loading. Given that two other plugins turn it back on, here are some things to check:
Besides Pods and the two mentioned plugins, are you running any plugins or a theme that attempt to configure the editor to be either block or classic, rather than allowing both? This can most easily be tested by switching to a default theme and disabling all other plugins temporarily.
Are there any errors in the browser JavaScript console?
After these, does clearing server cache, browser cache, or saving permalinks resolve the issue?
This is a brand new install of WordPress to test this problem.
There are no other themes installed, it’s the standard 2024 theme that comes with WordPress 6.5.
There is only one Pods wysiwyg field added to the standard page type. Besides the two plugins mentioned (Advanced Editor Tools, ACF), no other plugins are installed. Each of the additional plugins ‘fixes’ the problem whether they’re both activated or just one is activated.
Clearing Caches didn’t help, nor does Saving Permalinks.
I noticed these errors (shown in attached image) when inspecting the rendered page, but I get almost exactly the same errors if I disable Pods and set up the same kind of wysiwyg field using ACF (which works – I can type in the visual part), so can these errors be contributing to the problem?
Having this issue as well. Can’t use the custom WYSIWYG field combined with the block editor without a secondary plugin. Can’t even click on the visual part, and even if you put the text in the plain side, it appears blank when it loads the visual side.
Nothing showing in browser console or PHP error_log.
While the solutions are appreciated, it would be nice if this could be fixed within Pods so we can do it without adding more plugins.
