Posted a workaround first, then recent related posts surrounding this issue that used the same workaround.