This issue was fixed in this commit, which is included in the latest version of Discourse. It should be resolved after your next update (which I recommend doing as soon as possible because of the included security updates)
5 Likes