Fix showing Markdown field changes with 'None' values.
Review Request #6290 — Created Sept. 3, 2014 and submitted — Latest diff uploaded
When rendering a Markdown field in a change description box, we weren't
ensuring that the old or new values were strings. They could be None,
which is a valid value indicating there was no content before. This
would end up breakingrender_markdown()
.We now convert to an empty string if it's None.
Caused the breakage, using the Note to Reviewers extension. Saw that it was
fixed after this change.