Markdown post got converted to HTML!
-
I wrote this post using the new editor interface in Markdown:
http://codeyarns.com/2015/11/26/how-to-use-kinect-v2-on-windows/I had to upload an image for the post. So, I switched to Visual tab (isn’t that the only way to upload media now?), uploaded the image, inserted its HTML code into the post and switched the post back to HTML tab. Except for the image code, rest of the post was still in Markdown.
I completed the post, published it. When I clicked Edit below the post to make a correction, the post was in full HTML code instead of Markdown.
Should I use the old post editor if I need Markdown?
The blog I need help with is: (visible only to logged in users)
-
There’s a bug with Markdown in WordPress, which is entered into the HTML view of the Post/Page editing window. WP then convers to HTML, but if the view is then changed to Visual, the Markdown is converted into HTML so that it appears as raw Markdown text in the browser and is not converted back to Markdown text in the HTML view.
The only way to correct it is to replace the converted text in the HTML view with the original Markdown and republish it.
So if a Post/Page is showing as Markdown in the HTML view, do NOT switch to the Visual view, otherwise the above happens. It’s a total pain.
-
@ashwinn
No markdown support in the new editor is a known issue https://en.forums.wordpress.com/topic/editor-feedback?replies=739You cannot deactivate the new Beep Beep Boop editor but you do not have to use it. For locating the ways and means of accessing the legacy or classic pages for creating posts, editing posts, and for viewing stats see here > Navigating the Classic WordPress.COM interface http://onecoolsite.wordpress.com/2015/04/05/navigating-the-classic-wordpress-com-interface/
On the dashboard of your own blog at
Dashboard > Posts > All Posts > Add New
To create posts in the classic editorhttp://NAME_OF_BLOG.wordpress.com/wp-admin/post-new.php
On the dashboard of your own blog at
Dashboard > Posts > All Posts one can hover over any post title and click the Edit link. and proceed with editing. -
@ashwinn
NOTE: One has to replace – http://NAME_OF_BLOG.wordpress.com with the relevant URLOn the dashboard of your own blog at
Dashboard > Posts > All Posts > Add New
To create posts in the classic editorhttp://NAME_OF_BLOG.wordpress.com/wp-admin/post-new.php
http://codeyarns.com/wp-admin/post-new.php
On the dashboard of your own blog at
Dashboard > Posts > All Posts one can hover over any post title and click the Edit link. and proceed with editing. -
This also happens with self-hosted blogs not on wordpress.com.
Seems to me the best way to handle it is to have another view tab in the editor labelled Markdown, in which MD-text can be entered and converted to HTML, but not changed by changing the view away from the MD tab.
Make this so, #1!
-
This also happens with self-hosted blogs not on wordpress.com.
Right and we don’t provide support for those sites here at wordpress.COM. WordPress.COM and WordPress.ORG are completely separate and have different username accounts, logins, features, run different versions of some themes with the same names, and have separate support documentation and separate support forums. Read the differences here http://en.support.wordpress.com/com-vs-org/
If you don’t have a username account at WordPress.ORG account, then click http://wordpress.org/support/ and register one on the top right hand corner of the page that opens, https://wordpress.org/support/register.php so you can post to the support forums there.
Resetting your WordPress.ORG password http://codex.wordpress.org/Resetting_Your_Password
WordPress.org support docs are at https://codex.wordpress.org/Main_PageSee also https://apps.wordpress.org/support/
-
Right. Me bad, but WordPress.com login seems to work across everything and is required for Jetpack integration of self-hosted blogs.
Right hand not know what left hand doing?
-
Oh they know exactly what they are doing. All the changes are made here at wordpress.com first as we are the guinea pig testing platform. The Story Behind the New WordPress.com. https://developer.wordpress.com/2015/11/23/the-story-behind-the-new-wordpress-com
Then official announcements are made like this one https://en.forums.wordpress.com/topic/editor-feedback?replies=739 and the Calypso dancing starts over at wordpress.ORG as the koolaid is passed around while congratulations flow liberally through the social networks like Twitter. ;)
Meanwhile support issues are found tucked away in 25 page long threads threads like this one https://en.forums.wordpress.com/topic/editor-feedback?replies=739
-
Oops! Link correction I meant to post:
Then official announcements are made like this one https://en.blog.wordpress.com/2015/11/16/new-high-speed-editor/
-
-
Upgrades don’t make any difference at all.
After 2 years of coping with their faffing around https://en.blog.wordpress.com/2014/12/16/dashboard-update/ I chose to cancel both my domain mapping upgrades and no ads upgrades on both of my sites.
- The topic ‘Markdown post got converted to HTML!’ is closed to new replies.
WordPress.com Forums 