This question, closed yesterday, was bumped by its OP requesting reopen votes. I decided to roll back the edit (I know this doesn't 'unbump' it but that's not my point), but it seems the formatting has gone kaput and no longer works. However, if I click on 'edit', the formatting shows up OK in the editor's live preview. Resaving the edit doesn't fix the problem though.

This is my first rollback on a closed question, and it's also the first time I see this error so I'm wondering if it has anything to do with its closed status.

EDIT: R. Bemrose chipped in with an extra newline and the formatting is back. But I did experience the formatting bug when I rolled it back before that.

EDIT 2: waffles inadvertently uncovered this issue here on Meta, for this open question, so it's nothing to do with closed status then.

EDIT 3: gah, it just hit me again on another open question. I think SO doesn't like me rolling back edits anymore. Fixed it also by adding blank lines. I also edited the question title because it doesn't just affect closed questions.

EDIT 4: looks like this is affecting answers too, thanks Shog9.


  • Can you explain what formatting broke, exactly? As you mention, the revision history does not show the issue; moreover, I have done rollbacks on closed questions without seeing any noticeable deterioration, so knowing what exactly broke would help in trying to replicate it. – Grace Note Sep 3 '10 at 18:44
  • 1
    @Grace Note: all the formatting disappeared and the formatting characters showed up in raw plain text. – BoltClock's a Unicorn Sep 3 '10 at 18:46
  • 2
    It appeared as plain text with no line breaks. I didn't think to view the HTML source to see what it looked like. Even the link section at the bottom appeared in it. – Powerlord Sep 3 '10 at 18:53
  • 1
    Confirmed here: meta.stackexchange.com/questions/63270/… – Jon Seigel Sep 3 '10 at 21:27
  • 1
    I've seen this too. It's really getting on my nerves... – Yi Jiang Sep 9 '10 at 1:47
  • 2
    So this is just [status-wtf]? Hit me too today and its especially annoying when already dealing with a messy question. – Georg Fritzsche Sep 9 '10 at 10:56
  • 1
    Well, this just happened on Gaming earlier. Really made a mess of the question and drove me nuts. Wonder what the cause is... – Grace Note Sep 10 '10 at 19:09
  • 1
    @GraceN: fixed. – badp Sep 11 '10 at 15:08
  • 2
    Reproduced – Shog9 Sep 11 '10 at 17:21
  • 2
    @Shog9: on one of Welbog's posts at that!!! – BoltClock's a Unicorn Sep 11 '10 at 17:41
  • Heh... FWIW, the reason for the rollback was a previous bug that truncated long posts at an arbitrary point. – Shog9 Sep 11 '10 at 17:55
  • Screenshots of another occurrence – ændrük Sep 14 '10 at 18:36
  • 1
    My bad, will be fixed in the next deploy – waffles Sep 16 '10 at 4:26
  • 2
    fixed now (on meta) will be rolled out on the rest of the sites later – waffles Sep 16 '10 at 4:42
  • @waffles: thanks! Was that FOR REALS THIS WAS FIXED edit there to test the fix? :) – BoltClock's a Unicorn Sep 16 '10 at 7:04

It appears that post rendering is skipped after a rollback and the result is saved in a cache. Changing the source forces a rerendering and fixes the issue -- even if the change doesn't actually translate in a rendered difference.

You must log in to answer this question.

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