Hi,
that’s a known problem with v6.26.02 (aka latest-stable at the time of writing), it should come up if you search for it on this forum. It’s fixed in master and v6-26-00-patches and it will be fixed in the upcoming v6.26.04 (future latest-stable).
Cheers,
Enrico