> webworxshop opened this issue on 4 Dec 2020 Triple yikes. Though it looks like the issue was finally closed minutes ago: > Hi there, sorry, this issue was

> webworxshop opened this issue on 4 Dec 2020 Triple yikes. Though it looks like the issue was finally closed minutes ago: > Hi there, sorry, this issue was fixed in 5.17 (which hit 100% production on 7/21). There was another issue tracking this and it looks like I forgot to close this one. Still, that's a lot of time for such a bug to exist!