Thank you for pointing that out! We are aware of that issue (it happened during a content migration/reorganization) and need to fix it. We're tracking...