3

See this question. When published, the markdown does not render the same way it does in preview for edit mode. The numbered list does not continue when published, but appears to continue in preview. Moreover, the OP actually typed 2, but it still rendered as 1 which is puzzling.


Published


published markdown rendered


Editor Preview


preview editor markdown rendered

7

When that post was created, our Markdown parser ignored the numbers and always started new lists at 1. That has since changed, but the post has never been re-rendered to reflect that change, so it is still showing a cached copy of how it was rendered at the time it was posted.

If you simply make some completely frivolous change so that the system caches a new rendered copy, it will update to display the same as the preview.

  • Is there any process to automatically re-render cached markdown when the parser changes? I mean, will this eventually get cleaned up on its own, or does this require someone to make an intentional (hopefully non-frivolous) edit to render the proper results? – Michael Gaskill Jun 11 '16 at 5:02
  • @Michael No, everything is left alone because there's no way to determine which posts would actually be affected by a change. "Re-caching" is literally running a process which runs every single post on the network through the parser again and store the new ouput. Far easier to just let someone update it when they see it. – animuson Jun 11 '16 at 5:07

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .