Thanks for the post, Frisque.

This was an issue that our QA team caught as well, and it looks to be the result of a malfunctioning macro. It has since been fixed and should be showing up fine for 1.22c.