@GaryJ No reason to go around intended WP behavior when there’s another way, eh?