-
Notifications
You must be signed in to change notification settings - Fork 89
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
MD Disappearing on save #331
Comments
Update on this - it seems like this is only happening with custom post types. I can take the exact same content and paste it into a Post or into a custom post (which is enabled in the settings) and everything saves perfectly fine in the database. (Both have the MD in post_content_filtered and the html in post_content). The problem is when I open a saved post, that content on the page is in MD format. When I open a custom post type, that content is in html format. I'm guessing there is a function somewhere that is hooked into a post loading and is supposed to swap the post_content and post_content_filtered, but is only doing it for the Post type instead of all supported CPTs. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 2 days. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
I had the same problem with a regular post type |
Any issue will be ignored if you don't provide the following detailed information.
Describe the bug
After saving the post, the MD content no longer shows, but is converted to html. I have to manually click the Convert button each time I visit the page.
To reproduce
Steps to reproduce the behavior:
Expected behavior
It used to be that when the content saved it would stay as MD. I'm not sure what has changed, but I expect that the content automatically changes back to MD when the page loads.
Screenshots
Server environment
User environment
Additional context
I have tried copying the data to a local setup as well and the same thing happens. I updated that plugin to the latest version and have the same issue.
The text was updated successfully, but these errors were encountered: