Support » Everything else WordPress » Markdown bug (?) in plugin documentation.

  • Resolved Dan Rossiter


    In Document Gallery, one of my plugins, I’m having a hell of a time getting the first question in my Q&A section to bold. I’m using the same syntax as questions further down the page, but it isn’t working.

    I’ve tried a number of different things that I thought might work, but nothing seems to. Is this a markdown issue or am I being dense in some way?

    The issue can be seen here.


Viewing 5 replies - 1 through 5 (of 5 total)
  • Moderator Ipstenu (Mika Epstein)


    🏳️‍🌈 Halfelf Rogue & Plugin Review Team Rep

    It’s not true markdown and generally I use html for strong/em. The =’s are headers though 🙂

    Make sure your text is really pure text and not weirdly encoded by your text editor.

    If it were an encoding issue, it wouldn’t be isolated to a single header. If you look at the config (or the page linked in my initial post), there are numerous instances of the exact same syntax that work. With just one not working, surely it’s a parsing engine issue on the side…


    Since staff are apparently incapable of supporting their own product, I’ll go ahead and post the solution I finally stumbled into for anyone else who might run into this issue.

    The problem is that the header (=) notation requires all of the content to be on a single line. I had a long header so it was broken into two lines. Un-breaking the line solved the issue.




    Forum Moderator

    Since staff are apparently incapable of supporting their own product

    There are no “ staff”. Just lots of volunteers working within a custom, and ever evolving, network.


    I probably went a little overboard, but I’m frustrated by the first mod’s answer (or lack thereof). The answer showed no effort to solve a problem — a problem that I as an unpaid plugin developer for needed to resolve in order to provide a quality product to my (’s) users. I don’t get paid to develop my plugins, but I put effort into providing support to my users and in the event that I misunderstand a question or don’t provide a satisfactory answer the first time, I will go back and work with that user.

    Again, I probably overreacted, but that is where my frustration stemmed from. I do appreciate what you and the other mods do.


Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Markdown bug (?) in plugin documentation.’ is closed to new replies.