Skip to content

Conversation

widoz
Copy link

@widoz widoz commented Nov 26, 2017

No description provided.

@rmccue
Copy link
Member

rmccue commented Nov 28, 2017

Thanks for the PR!

I'm 99% certain that I did this intentionally, since the [info] block isn't parsed as Markdown when we import it.

Can you test this using Jetpack's Markdown support and see if it's parsed? You may need to also have the info shortcode registered.

@widoz
Copy link
Author

widoz commented Nov 28, 2017

@rmccue Uhm, I did the change since within the handbook the ul tag is malformed.
Btw, I'll perform the test you asked.

@rmccue
Copy link
Member

rmccue commented Nov 30, 2017

Right, but I think the better change would be to add the </ul>, because I think Markdown isn't parsed inside [info] shortcodes. (Not sure why it's ending up with < ul> as text, but I'd bet it's some sort of kses thing.)

@kadamwhite
Copy link
Contributor

kadamwhite commented Jan 11, 2018

@rmccue is correct, when testing with Jetpack Markdown the Info shortcode will not properly parse markdown so we can't use this syntax inside the shortcode tags. I'll close this and add in the </ul> instead.

@kadamwhite kadamwhite closed this Jan 11, 2018
@kadamwhite
Copy link
Contributor

Never mind, superseded by #11 !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants