( ! ) Warning: getimagesize(/srv/users/serverpilot/apps/curtismchale-personalsite/public/files/2013/07/logo.gif): failed to open stream: No such file or directory in /srv/users/serverpilot/apps/curtismchale-personalsite/public/wp-content/plugins/elevate-seo/src/facebook.php on line 49
Call Stack
#TimeMemoryFunctionLocation
10.0001355856{main}( ).../index.php:0
20.0001356144require( '/srv/users/serverpilot/apps/curtismchale-personalsite/public/wp-blog-header.php' ).../index.php:17
30.543016052096require_once( '/srv/users/serverpilot/apps/curtismchale-personalsite/public/wp-includes/template-loader.php' ).../wp-blog-header.php:19
40.545815982776include( '/srv/users/serverpilot/apps/curtismchale-personalsite/public/wp-content/themes/curtismchale-2018/single.php' ).../template-loader.php:74
50.545815982776get_header( ).../single.php:10
60.545815983904locate_template( ).../general-template.php:41
70.545815984064load_template( ).../template.php:647
80.545915984512require_once( '/srv/users/serverpilot/apps/curtismchale-personalsite/public/wp-content/themes/curtismchale-2018/header.php' ).../template.php:688
90.546215985264wp_head( ).../header.php:21
100.546215985264do_action( ).../general-template.php:2614
110.546215985640WP_Hook->do_action( ).../plugin.php:453
120.546215985640WP_Hook->apply_filters( ).../class-wp-hook.php:310
130.585916229880ElevatePlugin->handle_wp_head( ).../class-wp-hook.php:286
140.585916229880ElevatePlugin->_output_meta_fields( ).../elevate-class.php:2809
150.588816231216ElevatePlugin->_maybe_output_social_tags( ).../elevate-class.php:2594
160.588916232440ElevateFacebook->output_meta( ).../elevate-class.php:2363
170.589116232552getimagesize ( ).../facebook.php:49

Less in love with markdown

I love Markdown. It’s super easy to remember and write. I think that it looks less cluttered when you’re writing (especially links) and it gets a bunch of HTML markup out of your way.

logo

What I hate is the WordPress support for it in the editor. I’ve never found a plugin that works properly. Either we have issues with shortcodes that have more than one _ in them or we have issues with custom post types not picking up the markdown.

When the markdown isn’t parsed you end up with the user seeing all the funny marks in my copy. That is simply not acceptable.

At this point I’ve resolved to stop putting markdown in the WordPress editor. I still write in it in Byword but I copy the HTML out and paste that HTML in to the WordPress editor.

Have any of you found a great Markdown plugin for WordPress?

5 thoughts on “Less in love with markdown

  1. The plugin I’ve been using for some time now is Markdown On Save, but unfortunately as you outlined it too falls victim to some Shortcode issues (I think). I haven’t taken the time to fully flesh out where the issue is taking place, but what I usually run into isn’t so much a problem with parsing the Shortcode, it’s the handling of the whitespace around said shortcode(s). I usually end up with a bunch of empty paragraphs, or other issues with unwanted empty tags messing up the content around the Shortcode. I like how simple Markdown On Save is, and that if I decide to turn it off, I won’t lose a step due to the way it actually stores the content.

    I don’t use Shortcodes a lot, but when I do I’ve resorted to turning off Markdown and sticking with HTML myself (sometimes).

    1. I’ve had issues with Markdown on Save just not working with CPT’s. Specifically with my EDD store the content would look fine for a while then suddenly I’d realize the Markdown wasn’t getting parsed. I couldn’t ever get it to parse again either.

      I’m just planning on sticking with HTML in the post editor. At some point in the next 6 months I’ll simply remove the Markdown plugins since the Markdown content will be older by that point and not get as much traffic.

  2. Same here Curtis, I always copy my html out. I cannot stand this issue, it always seems to be a problem with WordPress. I stopped using shortcodes a longtime ago because of inconsistencies and now I create everything mostly using custom CSS and create custom page or post templates along with custom fields. I was spending more time fighting with WordPress than going custom. I also prefer not to use plugins as much as possible to avoid lag and more frustration.

    1. Plugins are not really a problem, bad code is the problem. You can have bad code in a theme just as easily as you can have it in a plugin. I just use well written plugins.

      I’m divided on shortcodes. There is a good reason to use them when you want to add complex functionality (like Easy Digital Downloads and WooCommerce) to themes. They are not an end all solution and need to be approached with great care.

Comments are closed.

To get a head start, join thousands of other men and Stop The Struggle.

Get my free eBook to help you stop working all the hours without traction.

You’ll also get a weekly email with good resources to help you do family with the same intention you do your work. Both need to run well if you want to win.

%d bloggers like this: