You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having an issue when importing and having a Markdown Extra formatter. Not sure if it's something from the integration branch or some setting.
The HTML/Markdown I'm importing contains the following amongst other things which is not exactly valid html.
When viewing the data as output by the markdownify function all looks good, yet when the entry is created the output on the frontend appears to be encoded, presumably when the Markdown Extra function is run to insert this data. What is most interesting however is the fact that when I re-save the entry through the backend this appears as a normal xml node not encoded. So I can then use XSLT to transform this fake tag into an image or something else as appropriate.
@brendo no it's practically the whole range Markdown, Markdown Extra, and Markdown Extra with Smarty Pants. Didn't try purifier as that wouldn't give me the flexibility I need. I'm not sure if it's something with the XML Importer possibly encoding these XML entities.
Actually I've got it down to the markdownify function supplier with teh XML Importer Helpers. More specifically htmlspecialchars temporarily I'm using an str_replace to revers < and > but not convinced that it is a robust solution.
Having an issue when importing and having a Markdown Extra formatter. Not sure if it's something from the integration branch or some setting.
The HTML/Markdown I'm importing contains the following amongst other things which is not exactly valid html.
When viewing the data as output by the markdownify function all looks good, yet when the entry is created the output on the frontend appears to be encoded, presumably when the Markdown Extra function is run to insert this data. What is most interesting however is the fact that when I re-save the entry through the backend this appears as a normal xml node not encoded. So I can then use XSLT to transform this fake tag into an image or something else as appropriate.
@brendo any idea where I should be looking?
The text was updated successfully, but these errors were encountered: