Hi James,
Not that I’m aware of. It was working just fine a few weeks ago, and then this happened. Other fields being used the exact same way on other post types / taxonomies are working just fine as well. Can’t seem to figure out why this one field would be having this problem.
