@nickciske Thanks for going above and beyond at looking into this issue even though the problem wasn’t with this plugin specifically. Indeed it looks like a site specific issue with the factors that you pointed out. I’ll look into what I can do to resolve those. Thanks for the support, I really appreciate it!
