Second completely unrelated issue reported in same task (tssst...), caused by missing doversion code of some changes in recent-ish 2.80 development (tsst... again). Proper fix for the issue (reverted rB8a5a8282ce48 was merely sweeping the dirt under the carpet...).