Thread

I’ve meant to get this documented, since it showed up on upgrading to 2.4, and repeated exactly on upgrade to 2.5. I presume it’s still there for 2.5.1.

There has been a force-behaviour workaround, but I went further when upgrading to 2.5 a few weeks ago, and tied down what’s causing it, which allows a much better way to go for those who have the problem.

The bug report is here, and contains both solutions.

Regards.
Clive

Hello narration,

Thanks for reporting this.

If you need anything else, please just let me know by opening a new thread.

Cheers,