∞
@toddgrotenhuis This is now fixed in the latest version of my plug-in (1.2.1). I used some modern shenanigans in the templates that the old Hugo (0.54) didn't like. Thanks again for the report, and sorry for the inconvenience.