[wp-meta] [Making WordPress.org] #2655: Code blocks escaped with backticks are not parsed in FAQ?
Making WordPress.org
noreply at wordpress.org
Fri Mar 31 06:22:08 UTC 2017
#2655: Code blocks escaped with backticks are not parsed in FAQ?
------------------------------+------------------
Reporter: GamerZ | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: Plugin Directory | Resolution:
Keywords: |
------------------------------+------------------
Comment (by dd32):
Looks like the Markdown parser is getting confused a bit here - but also
that it's being more strict than the previous one.
Although it previously worked, code blocks are not supposed to be
surrounded by a single backtick, instead according to the
[https://daringfireball.net/projects/markdown/syntax#precode Markdown
syntax] they're supposed to be indented (ie. see how
[https://gist.github.com/dd32/a0cc0bf2fcbb9931f3d573032cada012 github]
parses that readme)
We're using [https://michelf.ca/projects/php-markdown/extra/ Markdown
Extra] which adds extra syntaxes, such as [https://michelf.ca/projects
/php-markdown/extra/#fenced-code-blocks fenced code blocks] which should
help here.
There might be something else happening here though, because even after
changing it to a fenced code block, it still choked returning the
following, note the unescaped `<?php`.
{{{
<pre><code><?php if ( function_exists( 'get_pollanswers' ) ): ?>
<?php get_pollanswers(); ?>
<?php endif; ?>
</code></pre>
}}}
I'm not sure if this is being caused by the fact it's within a list
element, or if the library simply can't process code blocks properly.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/2655#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list