Closed elskeetro closed 1 year ago
I wonder if one of those other plugins is interfering. Pods doesn't manage the main content editor field itself, only telling WP whether to show it or not.
Based on your feedback, when Pods loads its own assets for the fields it creates, that loads the same assets needed by the content editor field too so now it shows.
Step one would be to check the browser dev tools console to see if there are any 404s or script errors when the content editor field exhibits this broken behavior.
Once you know what the error is, write that down for reference.
Next step would be to try disabling plugins to determine at which point it starts working. Leave Pods on during that process since that's your custom post type provider.
I tested this locally but could not reproduce this. Based on that and the last note I left -- I bet this may be one of the other plugins removing the TinyMCE script needed on that page (probably for their own purposes, but it accidentally applied to all other classic editor powered screens).
Closing topic due to inactivity. @elskeetro Feel free to reopen and reply to our comments.
Description
Client prefers WP Classic Editor environment.
The default description field that populates the @post_content values is not available in my pods, nor displaying in my existing pods template.
As a work around, I added a "temporary_description" field to the pod, set as a WYSIWYG visual editor. When I went to edit the content, the default field was now available.
Removing the "temporary_description" WYSIWYG field from the pod made the default field unavailable, once again.
Version
2.9.9
Testing Instructions
Screenshots / Screencast
Possible Workaround
Adding a WYSIWYG Visual Editor seems to make the post_content field and its content available again.
Site Health Information
Pods Package